Triple
T38132154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i360 observation tower |
E952251
|
entity |
| Predicate | maximumRangeOfView |
P186122
|
FINISHED |
| Object | up to 26 miles |
—
|
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: up to 26 miles | Statement: [i360 observation tower, maximumRangeOfView, up to 26 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeOfView Context triple: [i360 observation tower, maximumRangeOfView, up to 26 miles]
-
A.
viewDistance
chosen
Indicates the maximum distance from which an entity can see or visually perceive another entity or object.
-
B.
angleOfViewMax
Indicates the maximum angle or field of view within which something can be seen, captured, or effectively observed.
-
C.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
D.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
E.
maximumWorkingDistance
Indicates the greatest allowable or effective distance at which the specified work, operation, or interaction can be performed.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:21 p.m.