Triple

T17574916
Position Surface form Disambiguated ID Type / Status
Subject Hochtaunuskreis E428038 entity
Predicate contains P35 FINISHED
Object Neu-Anspach 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: Neu-Anspach | Statement: [Hochtaunuskreis, contains, Neu-Anspach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neu-Anspach
Context triple: [Hochtaunuskreis, contains, Neu-Anspach]
  • A. Neu-Anspach chosen
    Neu-Anspach is a small town in the Hochtaunus district of Hesse, Germany, known for its proximity to the Taunus mountains and the open-air museum Hessenpark.
  • B. Anspach
    Anspach is a surname most notably associated with American actress Susan Anspach, known for her roles in 1970s New Hollywood films.
  • C. Ravensburg
    Ravensburg is a historic town in southern Germany’s Baden-Württemberg state, known for its well-preserved medieval old town and as the namesake of the Ravensburger game and puzzle company.
  • D. Konstadt
    Konstadt is the historical German name for the Polish town of Wołczyn in the Opole Voivodeship.
  • E. Rosenheim
    Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4593403648190836266dbdb6cfc9f completed April 19, 2026, 4:25 a.m.
Created at: April 10, 2026, 5:50 a.m.