Triple

T8925240
Position Surface form Disambiguated ID Type / Status
Subject Hexham E212522 entity
Predicate hasTwinTown P919 FINISHED
Object Noyon E210279 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: Noyon | Statement: [Hexham, hasTwinTown, Noyon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noyon
Context triple: [Hexham, hasTwinTown, Noyon]
  • A. Noyon chosen
    Noyon is a historic town in northern France known for its Gothic cathedral and as the birthplace of Protestant reformer John Calvin.
  • B. Selenge
    Selenge is a northern Mongolian province (aimag) known for its agricultural lands and strategic location along the border with Russia.
  • C. Khorol
    Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
  • D. Bayan-Ölgii
    Bayan-Ölgii is a western Mongolian province known for its predominantly Kazakh population, rich nomadic culture, and dramatic Altai Mountain landscapes.
  • E. Tsalxhaan
    Tsalxhaan is the Tlingit name for Mount Fairweather, a prominent glaciated peak in the Fairweather Range of the Saint Elias Mountains on the Alaska–British Columbia border.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66547de881909ea9bfd104b32893 completed April 1, 2026, 12:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfba58e9ec81909141c516d05ac790 completed April 3, 2026, 1:02 p.m.
Created at: March 30, 2026, 6:57 p.m.