Triple

T14732602
Position Surface form Disambiguated ID Type / Status
Subject Iserlohn E346114 entity
Predicate hasCityDistrict P2709 FINISHED
Object Oestrich E823982 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: Oestrich | Statement: [Iserlohn, hasCityDistrict, Oestrich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oestrich
Context triple: [Iserlohn, hasCityDistrict, Oestrich]
  • A. Oestrich-Winkel chosen
    Oestrich-Winkel is a historic wine-growing town in Germany’s Rheingau region, renowned for its Riesling vineyards along the Rhine River.
  • B. Badenweiler
    Badenweiler is a spa town in southwestern Germany’s Black Forest region, known for its thermal baths and as the place where Russian writer Anton Chekhov died.
  • C. Gernsbach
    Gernsbach is a historic town in southwestern Germany’s Black Forest region, known for its medieval old town and picturesque setting along the Murg River.
  • D. Sporkenheim
    Sporkenheim is a district or locality within the town of Ingelheim am Rhein in Rhineland-Palatinate, Germany.
  • E. Odelzhausen
    Odelzhausen is a municipality in Bavaria, Germany, known for its historic castle and location along the Autobahn between Munich and Augsburg.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec72ea9348190817efcdaa973d7f7 completed April 14, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe9dba87c481908084c3cba5df3fcd completed May 9, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:29 a.m.