Triple
T644851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas statue |
E11218
|
entity |
| Predicate | figureHeight |
P9788
|
FINISHED |
| Object | about 15 feet |
—
|
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: about 15 feet | Statement: [Atlas statue, figureHeight, about 15 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: figureHeight Context triple: [Atlas statue, figureHeight, about 15 feet]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
-
D.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
-
E.
architecturalHeight
Indicates the measured vertical extent of a structure based on its architectural design, typically from the lowest significant level to the highest architecturally integral point, excluding non-architectural elements like antennas or masts.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f19f9a08190b0bf6e19b32427ff |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.