Triple
T17741815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Ottawa) |
E442876
|
entity |
| Predicate | hasGrandHall |
P128820
|
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: [Union Station (Ottawa), hasGrandHall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrandHall Context triple: [Union Station (Ottawa), hasGrandHall, yes]
-
A.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
B.
hasReceptionHall
Indicates that one entity possesses or includes a reception hall as part of its facilities or structure.
-
C.
hasMainHallType
Indicates the specific category or kind of main hall associated with an entity.
-
D.
hasStationHall
Indicates that one entity (typically a station) includes or is associated with a station hall area as part of its structure or facilities.
-
E.
hasMainHallShape
Indicates that an entity’s main hall has a specific geometric or structural shape.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47acd780c8190b1308ef0aca00f5c |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:09 a.m.