Triple

T14903129
Position Surface form Disambiguated ID Type / Status
Subject Breisach am Rhein E360057 entity
Predicate hasSubdivision P747 FINISHED
Object Oberrimsingen E1126677 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: Oberrimsingen | Statement: [Breisach am Rhein, hasSubdivision, Oberrimsingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberrimsingen
Context triple: [Breisach am Rhein, hasSubdivision, Oberrimsingen]
  • A. Münsingen
    Münsingen is a Swiss municipality in the canton of Bern, known for its scenic location in the Aare valley between Bern and Thun.
  • B. Niederrimsingen chosen
    Niederrimsingen is a village and district of the town Breisach am Rhein in the Breisgau-Hochschwarzwald region of Baden-Württemberg, Germany.
  • C. Riedlingen
    Riedlingen is a small historic town in the state of Baden-Württemberg in southern Germany, known for its well-preserved medieval old town on the Danube River.
  • D. Menzingen
    Menzingen is a municipality in the canton of Zug in central Switzerland, known for its rural landscape and location in the pre-Alpine region.
  • E. Obersiggenthal
    Obersiggenthal is a municipality in the canton of Aargau in northern Switzerland, located in the Limmat Valley near the city of Baden.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded60b24008190bd272c0d61329400 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fedd2046348190bcf8660bf3825b8f completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 2:11 a.m.