Triple
T4641397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Yellowknife |
E101663
|
entity |
| Predicate | dstRuleRegion |
P57546
|
FINISHED |
| Object | Canada Mountain Time |
—
|
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: Canada Mountain Time | Statement: [America/Yellowknife, dstRuleRegion, Canada Mountain Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstRuleRegion Context triple: [America/Yellowknife, dstRuleRegion, Canada Mountain Time]
-
A.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
B.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
C.
ruledFromRegion
Indicates that a ruling authority exercised control or governance over a domain while being based in or operating from a specific region.
-
D.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
E.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a91b7748190b0b080af76e7b39f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:14 p.m.