Triple
T35945490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixerbaceae |
E1039576
|
entity |
| Predicate | historicallyRecognizedInOrder |
P198903
|
FINISHED |
| Object | Crossosomatales |
—
|
NE NERFINISHED |
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: Crossosomatales | Statement: [Ixerbaceae, historicallyRecognizedInOrder, Crossosomatales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRecognizedInOrder Context triple: [Ixerbaceae, historicallyRecognizedInOrder, Crossosomatales]
-
A.
historicallyPlacedInOrder
chosen
Indicates that one entity is assigned a specific position or sequence in a historical ordering relative to other entities.
-
B.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
hasHistoricalRecognitionAs
Indicates that an entity is formally or widely acknowledged in a historical context as having a particular role, status, or identity.
-
E.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
Created at: May 3, 2026, 4:07 p.m.