Triple
T17175260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Transit |
E416842
|
entity |
| Predicate | usesTicketingZoneSystem |
P125194
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Calgary Transit, usesTicketingZoneSystem, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketingZoneSystem Context triple: [Calgary Transit, usesTicketingZoneSystem, no]
-
A.
ticketZoneSystem
chosen
Indicates that there is a specific fare or access zoning system governing how tickets are defined, priced, or validated within a transport or event context.
-
B.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
C.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
D.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
hasTicketingAuthority
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0cec448190b30466628a2ff23f |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.