Triple

T21016870
Position Surface form Disambiguated ID Type / Status
Subject Feldbrunnen E517700 entity
Predicate neighboringMunicipality P17964 FINISHED
Object Rüttenen 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: Rüttenen | Statement: [Feldbrunnen, neighboringMunicipality, Rüttenen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rüttenen
Context triple: [Feldbrunnen, neighboringMunicipality, Rüttenen]
  • A. Rüttenen chosen
    Rüttenen is a municipality in the canton of Solothurn in northwestern Switzerland.
  • B. Rutten
    Rutten is a small village in the Dutch province of Flevoland, located in the reclaimed polder region of the Netherlands.
  • C. Ruttenberg
    Ruttenberg is a surname most notably associated with Joseph Ruttenberg, an acclaimed cinematographer in American cinema.
  • D. Rucphen
    Rucphen is a municipality in the Dutch province of North Brabant, known for its rural character and proximity to the cities of Roosendaal and Breda.
  • E. Riederen
    Riederen is a locality within the municipality of Bolligen in the canton of Bern, Switzerland.
  • 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_69e0b50262b081909bc488937145eb73 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc5968c081909ae6407199858aba completed April 21, 2026, 4:26 a.m.
Created at: April 16, 2026, 1:54 p.m.