Triple

T4909271
Position Surface form Disambiguated ID Type / Status
Subject Mountain Daylight Time E110191 entity
Predicate IANAIdentifierExample P719 FINISHED
Object America/Edmonton E100144 NE 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: America/Edmonton | Statement: [Mountain Daylight Time, IANAIdentifierExample, America/Edmonton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: America/Edmonton
Context triple: [Mountain Daylight Time, IANAIdentifierExample, America/Edmonton]
  • A. America/Edmonton chosen
    America/Edmonton is the IANA time zone identifier representing the Mountain Time Zone region centered on Edmonton, Alberta, Canada.
  • B. America/Yellowknife
    America/Yellowknife is the IANA time zone identifier representing the Mountain Time observed in Yellowknife, the capital city of Canada’s Northwest Territories.
  • C. America/Regina
    America/Regina is the IANA time zone identifier representing the local time observed in Regina, Saskatchewan, 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/Vancouver
    America/Vancouver is the IANA time zone identifier representing Pacific Time for Vancouver and much of British Columbia, Canada.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd44132b94819088522d92beaadc78 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e99414081908c3d3283f563bba4 completed March 20, 2026, 3:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6fe098b081908e17d6d349b76364 completed March 21, 2026, 10:16 a.m.
Created at: March 20, 2026, 1:29 p.m.