Triple

T5155458
Position Surface form Disambiguated ID Type / Status
Subject Loyal Edmonton Regiment E116298 entity
Predicate city P40 FINISHED
Object Edmonton E23353 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: Edmonton | Statement: [Loyal Edmonton Regiment, city, Edmonton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edmonton
Context triple: [Loyal Edmonton Regiment, city, Edmonton]
  • A. Edmonton chosen
    Edmonton is the capital city of the Canadian province of Alberta, known for its major role in the energy sector and its extensive river valley park system.
  • B. Edmonton
    Edmonton is a historic suburban area in the London Borough of Enfield, formerly part of the county of Middlesex in England.
  • C. Calgary
    Calgary is a major city in the province of Alberta, Canada, known for its oil and gas industry, proximity to the Rocky Mountains, and the annual Calgary Stampede.
  • D. Calgary
    Calgary is a small coastal village on the Isle of Mull in Scotland, known for its scenic white-sand beach and surrounding natural beauty.
  • E. Lethbridge
    Lethbridge is a mid-sized city in southern Alberta, Canada, known for its coulee landscapes, windy climate, and role as a regional commercial and educational hub.
  • 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_69bd445d94788190b72e2cc563120995 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd78ddb01081909457ff4208eac4d7 completed March 20, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bed927ad5481909907c8a1764e9fd8 completed March 21, 2026, 5:45 p.m.
Created at: March 20, 2026, 1:44 p.m.