Triple

T21374035
Position Surface form Disambiguated ID Type / Status
Subject Ettenheim E527146 entity
Predicate nearbyCity P350 FINISHED
Object Lahr 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: Lahr | Statement: [Ettenheim, nearbyCity, Lahr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lahr
Context triple: [Ettenheim, nearbyCity, Lahr]
  • A. Lahr chosen
    Lahr is a town in southwestern Germany’s Baden-Württemberg region, situated near the Rhine River opposite Strasbourg and known for its historic center and proximity to the Black Forest.
  • B. Iffezheim
    Iffezheim is a municipality in southwestern Germany best known for its major horse racing track, one of the most important in the country.
  • C. Bruchsal
    Bruchsal is a town in the state of Baden-Württemberg in southwestern Germany, known for its baroque palace and asparagus cultivation.
  • D. Rastatt
    Rastatt is a historic town in southwestern Germany, known for its Baroque architecture and its role as the site of significant early 18th-century peace negotiations.
  • E. Blaubeuren
    Blaubeuren is a historic town in the Alb-Donau district of Baden-Württemberg, Germany, known for its medieval old town and the karst spring Blautopf.
  • 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_69e0b51e80808190ba5cb05667af02a9 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0b248508190aebeb671e55198da completed April 22, 2026, 11:27 a.m.
Created at: April 16, 2026, 5:10 p.m.