Triple
T34800693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver–Calgary |
E1003209
|
entity |
| Predicate | timeZoneAtEasternEnd |
P76187
|
FINISHED |
| Object | Mountain Time Zone |
—
|
NE NERFINISHED |
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: Mountain Time Zone | Statement: [Vancouver–Calgary, timeZoneAtEasternEnd, Mountain Time Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneAtEasternEnd Context triple: [Vancouver–Calgary, timeZoneAtEasternEnd, Mountain Time Zone]
-
A.
timeZoneAtUSEnd
Indicates the time zone that applies at the end point of a U.S.-based event, interval, or usage period.
-
B.
easternMostTimeZone
Indicates that the referenced time zone is the one located farthest to the east among a set of time zones.
-
C.
isEasternEndOf
chosen
Indicates that one entity forms or marks the easternmost end or boundary of another entity.
-
D.
adjacentTimeZoneEast
Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
-
E.
relativeToEasternTime
Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.