Triple
T19038257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal Tower |
E465933
|
entity |
| Predicate | observationDeckCapacity |
P89353
|
FINISHED |
| Object | up to several hundred visitors |
—
|
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: up to several hundred visitors | Statement: [Montreal Tower, observationDeckCapacity, up to several hundred visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationDeckCapacity Context triple: [Montreal Tower, observationDeckCapacity, up to several hundred visitors]
-
A.
observationDeckHeight
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
B.
observationDeckType
Indicates the specific kind or category of observation deck associated with an entity.
-
C.
standingCapacity
chosen
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
D.
observationDeckFloor
Indicates the specific floor or level of a building on which an observation deck is located.
-
E.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7fed99c81909495797c604db044 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.