Triple
T1958951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torre Latinoamericana |
E42335
|
entity |
| Predicate | wasTallestBuildingFrom |
P18568
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Torre Latinoamericana, wasTallestBuildingFrom, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTallestBuildingFrom Context triple: [Torre Latinoamericana, wasTallestBuildingFrom, 1956]
-
A.
wasTallestStructureIn
Indicates that one structure held the status of being the tallest within a specified place or during a specified time period.
-
B.
formerTallestBuildingInTheWorld
Indicates that a building once held, but no longer holds, the record for being the tallest building in the world.
-
C.
wasTallestBuildingInNewYorkUntil
Indicates that a building held the status of being the tallest building in New York up to a specified point in time.
-
D.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
-
E.
heldTallestBuildingTitleFrom
chosen
Indicates that one entity held the title of having the tallest building in the world (or a specified region) starting from a particular time.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.