Triple
T29087620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Tower observation deck |
E734159
|
entity |
| Predicate | locatedInSkyscraperRank |
P201492
|
FINISHED |
| Object | tallest building in Shanghai |
—
|
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: tallest building in Shanghai | Statement: [Shanghai Tower observation deck, locatedInSkyscraperRank, tallest building in Shanghai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSkyscraperRank Context triple: [Shanghai Tower observation deck, locatedInSkyscraperRank, tallest building in Shanghai]
-
A.
locatedInSkyscraper
Indicates that one entity is physically situated within or inside a skyscraper.
-
B.
locatedInSkyscraperDistrict
Indicates that an entity is situated within a district or area characterized by skyscrapers.
-
C.
isSkyscraperIn
Indicates that a skyscraper is located within or belongs to a specified geographic area or place.
-
D.
rankAmongTallestBuildings
Indicates that one building is among the tallest buildings within a specified group, area, or category.
-
E.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
- F. None of above. chosen
Provenance (4 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 28, 2026, 11:02 a.m.