Triple

T18978569
Position Surface form Disambiguated ID Type / Status
Subject arrondissement of Montbéliard E464360 entity
Predicate contains P35 FINISHED
Object Montbéliard 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: Montbéliard | Statement: [arrondissement of Montbéliard, contains, Montbéliard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Montbéliard
Context triple: [arrondissement of Montbéliard, contains, Montbéliard]
  • A. Montbéliard chosen
    Montbéliard is a historic town in eastern France, near the Swiss border, known for its former status as a Württemberg principality and its distinctive blend of French and German cultural influences.
  • B. Plombières
    Plombières is a municipality in the province of Liège in eastern Belgium, near the German and Dutch borders.
  • C. Cugny
    Cugny is a locality within the municipality of Bernex in the canton of Geneva, Switzerland.
  • D. Ferrière
    Ferrière is a French-language surname of Swiss origin borne by various notable individuals, including social worker and humanitarian Suzanne Ferrière.
  • E. Chassieu
    Chassieu is a commune in the Metropolis of Lyon in eastern France, known for its residential areas and proximity to the Lyon urban center.
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d621e3e08190b2d1d969ecaa380b completed April 20, 2026, 7:30 a.m.
Created at: April 10, 2026, noon