Triple

T18464472
Position Surface form Disambiguated ID Type / Status
Subject Mindelburg Castle E451121 entity
Predicate hasNearby P350 FINISHED
Object town of Mindelheim 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: town of Mindelheim | Statement: [Mindelburg Castle, hasNearby, town of Mindelheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: town of Mindelheim
Context triple: [Mindelburg Castle, hasNearby, town of Mindelheim]
  • A. Mindelheim chosen
    Mindelheim is a historic town in Bavaria, Germany, known for its well-preserved medieval old town and former status as a princely seat.
  • B. Gerlachsheim
    Gerlachsheim is a district of the town Lauda-Königshofen in the Main-Tauber-Kreis region of Baden-Württemberg, Germany.
  • C. Holzminden
    Holzminden is a town in Lower Saxony, Germany, known for its fragrance and flavor industry and its scenic location on the River Weser.
  • D. Sontheim
    Sontheim is a municipality in the Unterallgäu district of the Bavarian region of Germany, known for its rural character and location in the Allgäu area.
  • E. Haimhausen
    Haimhausen is a small municipality in Upper Bavaria, Germany, known for its historic castle and rural setting north of Munich.
  • 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_69e52a82920081909b2b89125db5982a completed April 19, 2026, 7:18 p.m.
Created at: April 10, 2026, 11:33 a.m.