Triple
T4190323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit of the Americas |
E89017
|
entity |
| Predicate | observationTowerHeight |
P5396
|
FINISHED |
| Object | 77 m |
—
|
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: 77 m | Statement: [Circuit of the Americas, observationTowerHeight, 77 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationTowerHeight Context triple: [Circuit of the Americas, observationTowerHeight, 77 m]
-
A.
observationTowerBuiltIn
Indicates that an observation tower was constructed within or during a specific location or time period.
-
B.
observationDeckHeight
chosen
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
C.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
D.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
E.
observationTowerDesign
Indicates a design relationship in which one entity serves as the architectural or structural design for an observation tower associated with another entity.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.