Triple
T20696724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shot |
E508679
|
entity |
| Predicate | hasHeightRange |
P122621
|
FINISHED |
| Object | medium tower height |
—
|
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: medium tower height | Statement: [Space Shot, hasHeightRange, medium tower height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightRange Context triple: [Space Shot, hasHeightRange, medium tower height]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
altitudeRange_m
chosen
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
C.
shoulderHeightRange
Indicates the range of vertical height measured from the ground to an entity’s shoulders.
-
D.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1123d7c81908a1d16923437266d |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:10 p.m.