Triple

T10694927
Position Surface form Disambiguated ID Type / Status
Subject Weißenfels E252109 entity
Predicate twinTown P1072 FINISHED
Object Mâcon E173944 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: Mâcon | Statement: [Weißenfels, twinTown, Mâcon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mâcon
Context triple: [Weißenfels, twinTown, Mâcon]
  • A. Mâcon chosen
    Mâcon is a historic town in eastern France’s Burgundy region, known for its wine production and picturesque setting along the Saône River.
  • B. Bourges
    Bourges is a historic city in central France known for its well-preserved medieval architecture and its UNESCO-listed Gothic cathedral, Saint-Étienne.
  • C. Dijon
    Dijon is a historic city in eastern France renowned for its rich architectural heritage, former status as the capital of the Duchy of Burgundy, and its famous mustard.
  • D. Chapeauroux
    Chapeauroux is a river in central France that flows through the Massif Central before joining the Allier.
  • E. Troyes
    Troyes is a historic city in northeastern France, known for its well-preserved medieval old town, half-timbered houses, and Gothic churches.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fd39c3788190bb7cd0acf8b6efdd completed April 9, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69f470cbce14819099d47d468ae61df7 completed May 1, 2026, 9:22 a.m.
Created at: April 8, 2026, 9:11 p.m.