Triple

T21393832
Position Surface form Disambiguated ID Type / Status
Subject Metzingen E527727 entity
Predicate hasTwinTown P919 FINISHED
Object Noyon NE NERFINISHED

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: [Metzingen, hasTwinTown, Noyon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noyon
Context triple: [Metzingen, 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. Toghrïl
    Toghrïl was a prominent 11th-century Seljuk leader and sultan who played a key role in establishing Seljuk dominance in the Islamic world.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee62cd30f08190aba90afed6116a2a completed April 26, 2026, 7:09 p.m.
Created at: April 16, 2026, 5:13 p.m.