Triple
T12823101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jardine House |
E306580
|
entity |
| Predicate | tallestBuildingStartYear |
P106538
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Jardine House, tallestBuildingStartYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tallestBuildingStartYear Context triple: [Jardine House, tallestBuildingStartYear, 1972]
-
A.
formerTallestBuildingInTheWorld
Indicates that a building once held, but no longer holds, the record for being the tallest building in the world.
-
B.
formerTallestBuildingIn
Indicates that a building was once the tallest building within a specified place or region, but no longer holds that status.
-
C.
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.
-
D.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
-
E.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9fcc8c8190a926ab0481d28f14 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:32 p.m.