Triple

T16571507
Position Surface form Disambiguated ID Type / Status
Subject Mount Rundle E402598 entity
Predicate locatedNear P294 FINISHED
Object Canmore E659464 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: Canmore | Statement: [Mount Rundle, locatedNear, Canmore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Canmore
Context triple: [Mount Rundle, locatedNear, Canmore]
  • A. Canmore
    Canmore is the online database of Scotland’s national record of the historic environment, documenting archaeological sites, buildings, and maritime heritage.
  • B. Canmore chosen
    Canmore is a mountain town in Alberta, Canada, known for its scenic location in the Canadian Rockies near Banff National Park and its popularity for outdoor recreation.
  • C. Anmore
    Anmore is a small semi-rural village in Metro Vancouver, British Columbia, known for its forested setting and proximity to outdoor recreation areas.
  • D. Banff
    Banff is a resort town in the Canadian Rockies of Alberta, known for its stunning mountain scenery, hot springs, and role as a gateway to outdoor recreation in Banff National Park.
  • E. Banff
    Banff is a historic town in Aberdeenshire, Scotland, known for its coastal setting on the Moray Firth and its well-preserved Georgian architecture.
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35958d49c8190b995188240fb355b completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0084b077f481909796b5b60f501239 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:16 a.m.