Triple
T15663321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornithomimus |
E376621
|
entity |
| Predicate | bodyPlanComparedTo |
P119658
|
FINISHED |
| Object | ostrich |
—
|
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: ostrich | Statement: [Ornithomimus, bodyPlanComparedTo, ostrich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPlanComparedTo Context triple: [Ornithomimus, bodyPlanComparedTo, ostrich]
-
A.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
B.
plannedAgainst
Indicates that an entity has formulated or coordinated plans targeting another entity, typically with opposing or adversarial intent.
-
C.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
D.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
E.
reconstructionPlanBy
Indicates that a specific reconstruction plan is created, authored, or provided by a particular agent or entity.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0e2668819092e52712cddd0721 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.