Triple

T17403624
Position Surface form Disambiguated ID Type / Status
Subject Ostermundigen E423156 entity
Predicate hasTwinTown P919 FINISHED
Object Böhlen 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: Böhlen | Statement: [Ostermundigen, hasTwinTown, Böhlen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Böhlen
Context triple: [Ostermundigen, hasTwinTown, Böhlen]
  • A. Böhlen chosen
    Böhlen is a small town in the Leipzig district of Saxony, Germany, known for its lignite mining and power generation industries.
  • B. Borgholzhausen
    Borgholzhausen is a small town in North Rhine-Westphalia, Germany, known for its location on the Teutoburg Forest and its historical ties to the former County of Ravensberg.
  • C. Obergum
    Obergum is a small neighborhood or former village that is now part of the town of Winsum in the province of Groningen, the Netherlands.
  • D. Kulmbach
    Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
  • E. Trostberg
    Trostberg is a small Bavarian town in southeastern Germany known for its historic old town and chemical industry.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b051cc48190872278ee0b52240d completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:45 a.m.