Triple
T7823744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commerzbank Tower |
E181193
|
entity |
| Predicate | tallestBuildingStatusStart |
P52363
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Commerzbank Tower, tallestBuildingStatusStart, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tallestBuildingStatusStart Context triple: [Commerzbank Tower, tallestBuildingStatusStart, 1997]
-
A.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
-
B.
formerTallestBuildingIn
chosen
Indicates that a building was once the tallest building within a specified place or region, but no longer holds that status.
-
C.
rankAmongTallestBuildings
Indicates that one building is among the tallest buildings within a specified group, area, or category.
-
D.
buildingHeight
Indicates the vertical extent or height measurement of a building.
-
E.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa0abff08190b0245ceca5f20cae |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:42 p.m.