Triple
T8467050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glires |
E200189
|
entity |
| Predicate | includesExtantOrders |
P83719
|
FINISHED |
| Object | Lagomorpha |
—
|
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: Lagomorpha | Statement: [Glires, includesExtantOrders, Lagomorpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExtantOrders Context triple: [Glires, includesExtantOrders, Lagomorpha]
-
A.
hasStandingOrders
Indicates that an entity has pre-authorized, recurring instructions or arrangements in place to be executed automatically under specified conditions.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
recognizesOrders
Indicates that one entity formally acknowledges and accepts the orders or directives issued by another entity.
-
D.
establishedForOrder
Indicates that something has been created or set up specifically to serve, support, or fulfill a particular order.
-
E.
orderDisplayed
Indicates that a particular order is currently being shown or presented in a user interface or display context.
- F. None of above. chosen
Provenance (4 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:11 p.m.