Triple
T3524142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titanosauria |
E74497
|
entity |
| Predicate | typicalBodyPlan |
P3595
|
FINISHED |
| Object | large quadrupedal herbivore |
—
|
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: large quadrupedal herbivore | Statement: [Titanosauria, typicalBodyPlan, large quadrupedal herbivore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyPlan Context triple: [Titanosauria, typicalBodyPlan, large quadrupedal herbivore]
-
A.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
B.
typicalBodyType
chosen
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
C.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
D.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
-
E.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.