Triple
T37213859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachiosauridae |
E922678
|
entity |
| Predicate | shoulderHeightRelativeToHips |
P126520
|
FINISHED |
| Object | higher shoulders than hips |
—
|
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: higher shoulders than hips | Statement: [Brachiosauridae, shoulderHeightRelativeToHips, higher shoulders than hips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoulderHeightRelativeToHips Context triple: [Brachiosauridae, shoulderHeightRelativeToHips, higher shoulders than hips]
-
A.
estimatedHeightAtHipsInMeters
Indicates the estimated vertical height, measured in meters, of an entity at the level of its hips.
-
B.
hasShoulderThatIsHighestPointOf
chosen
Indicates that an entity’s shoulder is the highest physical point or elevation on that entity.
-
C.
shoulderHeightRange
Indicates the range of vertical height measured from the ground to an entity’s shoulders.
-
D.
typicalShoulderLine
Indicates that one entity has a shoulder line that is characteristic or standard for the type, style, or category represented by the other entity.
-
E.
hasShoulderDiameter
Indicates the diameter measurement of an entity’s shoulder region or shoulder-related feature.
- 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.