Triple
T36697203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas |
E906123
|
entity |
| Predicate | heightAtNormalSize |
P9788
|
FINISHED |
| Object | approximately 6 feet 3 inches |
—
|
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: approximately 6 feet 3 inches | Statement: [Atlas, heightAtNormalSize, approximately 6 feet 3 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightAtNormalSize Context triple: [Atlas, heightAtNormalSize, approximately 6 feet 3 inches]
-
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.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
E.
approximateMaximumHeight
Indicates the estimated upper limit of an entity’s height, rather than an exact measured value.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7eb20548190a946a7257993b2a8 |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.