Triple

T8600815
Position Surface form Disambiguated ID Type / Status
Subject Landkreis Biberach E203668 entity
Predicate hasMunicipality P847 FINISHED
Object Riedlingen E757549 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: Riedlingen | Statement: [Landkreis Biberach, hasMunicipality, Riedlingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riedlingen
Context triple: [Landkreis Biberach, hasMunicipality, Riedlingen]
  • A. Riedlingen chosen
    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.
  • B. Vaterstetten
    Vaterstetten is a municipality in the district of Ebersberg near Munich in Bavaria, Germany, known as a residential suburb with strong transport links to the Bavarian capital.
  • C. Rheinsfelden
    Rheinsfelden is a locality in the canton of Zurich, Switzerland, situated near the confluence of the Glatt River with the Rhine.
  • D. Steißlingen
    Steißlingen is a municipality in the district of Konstanz in the state of Baden-Württemberg in southern Germany.
  • E. Riehe
    Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
  • 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46d8ff408190acc7cd8dc99b2689 completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0542fccd081908e1359cc71ba6774 completed April 3, 2026, 11:58 p.m.
Created at: March 30, 2026, 6:24 p.m.