Triple
T24299567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 85 Sky Tower |
E606054
|
entity |
| Predicate | wasTallestBuildingInTaiwan |
P52363
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [85 Sky Tower, wasTallestBuildingInTaiwan, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTallestBuildingInTaiwan Context triple: [85 Sky Tower, wasTallestBuildingInTaiwan, yes]
-
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.
wasTallestStructureIn
Indicates that one structure held the status of being the tallest within a specified place or during a specified time period.
-
D.
wasTallestBuildingOfType
Indicates that a building held the status of being the tallest among all buildings of a specified type (e.g., category, function, or classification) during a given context or time period.
-
E.
isTallestTowerIn
Indicates that one tower is the tallest tower within a specified location or set of towers.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915d8ac881908d71ba529e30f434 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.