Triple

T17206564
Position Surface form Disambiguated ID Type / Status
Subject Gitxsan people E417617 entity
Predicate hasSettlement P1068 FINISHED
Object Old Hazelton E417623 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: Old Hazelton | Statement: [Gitxsan people, hasSettlement, Old Hazelton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Hazelton
Context triple: [Gitxsan people, hasSettlement, Old Hazelton]
  • A. Old Hazelton chosen
    Old Hazelton is a historic village in northwestern British Columbia, Canada, closely associated with Gitxsan First Nation culture and history.
  • B. Hazelwood House
    Hazelwood House is a notable building in Sligo, Ireland, recognized as an important example of 18th-century country house architecture.
  • C. Hazeldean
    Hazeldean is a rural locality and small town situated within Queensland’s Somerset Region in Australia.
  • D. Hazell Stand
    Hazell Stand is a spectator seating section at Rodney Parade stadium, used primarily for watching rugby and football matches.
  • E. Hazelbrook
    Hazelbrook is a small residential town and village in the Blue Mountains region of New South Wales, Australia, known for its bushland setting and nearby waterfalls.
  • 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_69d886d6ba8c819093215917b3d01689 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dc193488190a2c5a48ce7f631a9 completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a015fde8ba08190ae88dc9ea3366a68 completed May 11, 2026, 4:49 a.m.
Created at: April 10, 2026, 5:38 a.m.