Triple

T21349802
Position Surface form Disambiguated ID Type / Status
Subject Eigeltingen E526443 entity
Predicate hasSubdivision P747 FINISHED
Object Honstetten 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: Honstetten | Statement: [Eigeltingen, hasSubdivision, Honstetten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Honstetten
Context triple: [Eigeltingen, hasSubdivision, Honstetten]
  • A. Engelhartstetten
    Engelhartstetten is a municipality in Lower Austria known for its rural character and proximity to the Slovak border and the Danube River.
  • B. Hirschstetten
    Hirschstetten is a residential and partly industrial neighborhood in Vienna, Austria, known for its local gardens and suburban character within the district of Donaustadt.
  • C. Hochstetten
    Hochstetten is a locality within the town of Breisach am Rhein in the Baden-Württemberg region of southwestern Germany.
  • D. Heuchstetten chosen
    Heuchstetten is a village-level subdivision of the municipality of Gerstetten in the German state of Baden-Württemberg.
  • E. Thunstetten
    Thunstetten is a municipality in the Oberaargau region of the canton of Bern in Switzerland, known for its rural character and historic Thunstetten Castle.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8ad30512081909012ce318fa67679 completed April 22, 2026, 11:12 a.m.
Created at: April 16, 2026, 5:03 p.m.