Triple

T18459709
Position Surface form Disambiguated ID Type / Status
Subject Rheinbach E450998 entity
Predicate hasSubdivision P747 FINISHED
Object Flerzheim 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: Flerzheim | Statement: [Rheinbach, hasSubdivision, Flerzheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Flerzheim
Context triple: [Rheinbach, hasSubdivision, Flerzheim]
  • A. Flerzheim chosen
    Flerzheim is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • B. Elbling
    Elbling is an ancient white wine grape variety primarily cultivated in Germany and Luxembourg, known for producing light, crisp, and high-acidity wines.
  • C. Hohenroth
    Hohenroth is a municipality in the Rhön-Grabfeld district of northern Bavaria, Germany, known for its rural setting near the Rhön Mountains.
  • D. Sormitz
    The Sormitz is a river in Thuringia, Germany, known for flowing through towns such as Leutenberg before joining the Saale.
  • E. Blatzheim
    Blatzheim is a village and district within the town of Kerpen in North Rhine-Westphalia, Germany.
  • 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a7cdb5c8190a399f0e4052f7d1f completed April 19, 2026, 7:18 p.m.
Created at: April 10, 2026, 11:33 a.m.