Triple

T29851940
Position Surface form Disambiguated ID Type / Status
Subject Phaseoleae E758088 entity
Predicate containsTaxon P9413 FINISHED
Object Sphenostylis
Sphenostylis is a small genus of flowering legumes native to Africa, known for species such as the African yam bean that are cultivated for their edible seeds and tubers.
E1889682 NE 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: Sphenostylis | Statement: [Phaseoleae, containsTaxon, Sphenostylis]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sphenostylis
Triple: [Phaseoleae, containsTaxon, Sphenostylis]
Generated description
Sphenostylis is a small genus of flowering legumes native to Africa, known for species such as the African yam bean that are cultivated for their edible seeds and tubers.

Provenance (5 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_69f2245a82cc8190a387e7d0118d710b completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f67648f35c8190ab466e413b6dbcb5 completed May 2, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a26f1c343f481909356a0701d58544b completed June 8, 2026, 4:45 p.m.
NEDg Description generation batch_6a26f3db3c4c8190afee1a0b06ade0fd completed June 8, 2026, 4:54 p.m.
NED2 Entity disambiguation (via description) batch_6a26f46b6b048190ae3168913b1b1ce8 completed June 8, 2026, 4:57 p.m.
Created at: April 29, 2026, 5:44 p.m.