Triple
T5887348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Tower |
E130895
|
entity |
| Predicate | wasTallestIn |
P30550
|
FINISHED |
| Object | Calgary upon completion |
—
|
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: Calgary upon completion | Statement: [Calgary Tower, wasTallestIn, Calgary upon completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTallestIn Context triple: [Calgary Tower, wasTallestIn, Calgary upon completion]
-
A.
isOneOfTallestIn
Indicates that an entity is among the tallest members within a specified group, set, or location.
-
B.
wasTallestStructureIn
chosen
Indicates that one structure held the status of being the tallest within a specified place or during a specified time period.
-
C.
replacedByAsTallest
Indicates that one entity has superseded another as the tallest among a relevant group or category.
-
D.
heldTallestStructureTitleFrom
Indicates that an entity held the title of being the tallest structure for a specified time period starting from a given point.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.