Triple
T19230914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Burgundy |
E480867
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | America/Toronto |
—
|
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: America/Toronto | Statement: [Little Burgundy, timeZone, America/Toronto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: America/Toronto Context triple: [Little Burgundy, timeZone, America/Toronto]
-
A.
America/Toronto
chosen
America/Toronto is the primary Eastern Time Zone designation used for major cities in Ontario, Canada, including Toronto and Montreal.
-
B.
America/Glace_Bay
America/Glace_Bay is an IANA time zone identifier representing the local time for Glace Bay, Nova Scotia, Canada, in the Atlantic Time Zone.
-
C.
America/Montreal
America/Montreal is the IANA time zone identifier corresponding to Eastern Time as observed in Montreal and much of the province of Quebec, Canada.
-
D.
America/Winnipeg
America/Winnipeg is the IANA time zone identifier representing the local time for Winnipeg, Manitoba, Canada, in the Central Time Zone.
-
E.
America/Moncton
America/Moncton is the IANA time zone identifier representing the local time for Moncton, New Brunswick, Canada.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9ce5e081909df994841ce476d5 |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 10, 2026, 1:25 p.m.