Triple

T21280391
Position Surface form Disambiguated ID Type / Status
Subject Dillingen an der Donau E524504 entity
Predicate twinTown P1072 FINISHED
Object Bondeno 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: Bondeno | Statement: [Dillingen an der Donau, twinTown, Bondeno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bondeno
Context triple: [Dillingen an der Donau, twinTown, Bondeno]
  • A. Bondeno chosen
    Bondeno is a municipality in northern Italy’s Emilia-Romagna region, known for its agricultural landscape and location within the Province of Ferrara.
  • B. Bondy
    Bondy is a suburban commune in the northeastern outskirts of Paris, France, served by regional rail and other public transport links into the capital.
  • C. Bondo
    Bondo is a town in western Kenya’s Nyanza region, known as an administrative and commercial center near Lake Victoria.
  • D. Bondo
    Bondo is a town located in the northeastern part of the Democratic Republic of the Congo.
  • E. Bondojito
    Bondojito is a station on Mexico City’s Metro system, serving passengers on Line 4 in the northern part of the city.
  • 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_69e0b516293c819089458ea2ec85f85e completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d186988190a5b16fcb669ece9f completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:02 p.m.