Triple
T37213861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachiosauridae |
E922678
|
entity |
| Predicate | tailRelativeToNeck |
P63385
|
FINISHED |
| Object | tail shorter than neck in many members |
—
|
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: tail shorter than neck in many members | Statement: [Brachiosauridae, tailRelativeToNeck, tail shorter than neck in many members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailRelativeToNeck Context triple: [Brachiosauridae, tailRelativeToNeck, tail shorter than neck in many members]
-
A.
tailCharacteristic
chosen
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
B.
neckFeathering
Indicates that one entity has feathers located on or covering the neck region of another entity (or itself).
-
C.
headRetraction
Indicates a relationship where an entity pulls or draws its head back from a previous position.
-
D.
hasTailShape
Indicates that an entity possesses a tail with a specific shape or form.
-
E.
tailLocation
Indicates the spatial position or placement of an entity’s tail relative to a reference frame or another object.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.