Triple
T22237336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton City Centre Airport |
E549624
|
entity |
| Predicate | closedToScheduledTraffic |
P146854
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Edmonton City Centre Airport, closedToScheduledTraffic, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToScheduledTraffic Context triple: [Edmonton City Centre Airport, closedToScheduledTraffic, 2010]
-
A.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
B.
closedToMotorTraffic
Indicates that a route, road, or path is not accessible for use by motor vehicles.
-
C.
closedToAllTraffic
Indicates that the subject is not accessible or usable by any type of traffic.
-
D.
closedToCivilianTraffic
Indicates that access along a route or at a location is restricted so that civilian vehicles or pedestrians are not allowed to use it.
-
E.
closedToTrafficDuringRepairs
Indicates that an entity (such as a road or route) is not accessible for traffic for the duration of repair or maintenance work.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13210eb9c8190bc40d06c393e0d9a |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:38 p.m.