Triple
T4498975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbeya |
E100769
|
entity |
| Predicate | describedAsGenusOf |
P9413
|
FINISHED |
| Object | flowering plants |
—
|
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: flowering plants | Statement: [Barbeya, describedAsGenusOf, flowering plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsGenusOf Context triple: [Barbeya, describedAsGenusOf, flowering plants]
-
A.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
B.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
C.
genusIncludes
chosen
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
D.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
E.
officiallyDescribedAs
Indicates that an entity is formally characterized or defined using a specific description in an official or authoritative context.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c29868819097633c7cd398e865 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.