You can call Lupedia using either POST or GET request methods.
The requests should be sent to the following URLs, according to the desired output:
| parameter | values | default | description |
|---|---|---|---|
lookupText |
a UTF-8 string | no default | The text to look up |
lang |
See ISO 639-1 codes below | en | Language for lookup text, can be specified multiple times |
threshold |
0.00 ~ 1.00 | 0.70 | Weight threshold, matches with weights below the threshold will be filtered out |
dataset |
URI describing dataset, see list below | all datasets | Datasets to match to |
skip_sh3 |
true or false | true | Skip matches shorter than 3 symbols |
skip_stp |
true or false | true | Skip matches that are stop-words |
keep_fnl |
true or false | true | Keep only first and longest match at given point |
skip_ldata |
true or false | false | Skip matching position and return a list of distinct entities (JSON/XML only) |
single_match |
true or false | false | Single greedy match only |
keep_highest |
true or false | true | Keep only matches with highest weight |
keep_specific |
true or false | true | Keep only the most specific class |
case_sensitive |
true or false | true | Case sensitive matching |
graph |
true or false | false | Graph enrichment mode; the found entities will be enriched further by following relations in the LOD graph (currently only DBpedia) |
The following DBpedia classes and their subclasses are available:
If you specify a class that has subclasses, the search results will include the subclasses as well.
The following experimental LinkedMDB classes are available: