Triple
T36554139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Finsch |
E901650
|
entity |
| Predicate | hasPartOfNameInTaxon |
P189882
|
FINISHED |
| Object | Finschia |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Finschia | Statement: [Otto Finsch, hasPartOfNameInTaxon, Finschia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartOfNameInTaxon Context triple: [Otto Finsch, hasPartOfNameInTaxon, Finschia]
-
A.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
-
B.
includesExampleTaxon
Indicates that a taxonomic group or concept contains a specific taxon used as an illustrative or representative example.
-
C.
hasRelatedTaxon
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
D.
hasEponymousTaxon
chosen
Indicates that an entity has a taxonomic group (such as a species or genus) that is named after it.
-
E.
includesTaxaWith
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:11 p.m.