Triple

T22150889
Position Surface form Disambiguated ID Type / Status
Subject Bonheiden E547408 entity
Predicate hasMunicipalSeat P1474 FINISHED
Object Bonheiden (town) 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: Bonheiden (town) | Statement: [Bonheiden, hasMunicipalSeat, Bonheiden (town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bonheiden (town)
Context triple: [Bonheiden, hasMunicipalSeat, Bonheiden (town)]
  • A. Bonheiden chosen
    Bonheiden is a municipality in the Belgian province of Antwerp, known as a residential community near the city of Mechelen.
  • B. Welkenraedt town
    Welkenraedt town is the central urban settlement and administrative hub of the municipality of Welkenraedt in the province of Liège, Belgium.
  • C. Neidingen
    Neidingen is a small locality in present-day Germany historically noted as the place where the Carolingian emperor Charles the Fat died.
  • D. Hedingen
    Hedingen is a small municipality in the canton of Zurich in Switzerland, situated in the district of Affoltern within the Albis region.
  • E. Bollodingen
    Bollodingen is a small village in the canton of Bern, Switzerland, situated in the Oberaargau region.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f37dac8190a7cecb12f4271515 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.