Triple

T22530276
Position Surface form Disambiguated ID Type / Status
Subject Roth district E557013 entity
Predicate hasMunicipality P847 FINISHED
Object Hilpoltstein 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: Hilpoltstein | Statement: [Roth district, hasMunicipality, Hilpoltstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hilpoltstein
Context triple: [Roth district, hasMunicipality, Hilpoltstein]
  • A. Hilpoltstein chosen
    Hilpoltstein is a historic town in Bavaria, Germany, known for its medieval castle ruins and picturesque old town.
  • B. Ottenheim
    Ottenheim is a village in southwestern Germany that now forms part of the municipality of Schwanau in the state of Baden-Württemberg.
  • C. Steinheim
    Steinheim is a locality within the Bavarian town of Dillingen an der Donau in southern Germany.
  • D. Friedrichstein
    Friedrichstein is a district or neighborhood within the spa town of Bad Wildungen in the state of Hesse, Germany.
  • E. Kottingbrunn
    Kottingbrunn is a market town in Lower Austria known for its historic castle complex and location within the Baden district south of Vienna.
  • 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_69e11e57483c8190b0887c4f8ff26446 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ed6734881908abbbee477dfab98 completed April 29, 2026, 1:28 a.m.
Created at: April 16, 2026, 8:51 p.m.