Triple

T16482270
Position Surface form Disambiguated ID Type / Status
Subject Pfäfers E400348 entity
Predicate neighboringMunicipality P17964 FINISHED
Object Haldenstein E190885 NE FINISHED

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: Haldenstein | Statement: [Pfäfers, neighboringMunicipality, Haldenstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haldenstein
Context triple: [Pfäfers, neighboringMunicipality, Haldenstein]
  • A. Haldenstein chosen
    Haldenstein is a small Swiss village in the canton of Graubünden, known in architecture circles as the longtime base of renowned architect Peter Zumthor.
  • B. Havenstein
    Havenstein is a German surname most notably associated with Rudolf Havenstein, the president of the Reichsbank during Germany’s hyperinflation period after World War I.
  • C. Hermannstein
    Hermannstein is a district of the German city of Wetzlar in the state of Hesse.
  • D. Hartenstein
    Hartenstein is a small town in the Free State of Saxony in eastern Germany, known for its historic architecture and scenic location near the Ore Mountains.
  • E. Hohnstein
    Hohnstein is a small historic town in Saxony, Germany, known for its medieval castle and scenic location in the Saxon Switzerland region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d883813098819084f5409539723b59 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e03643881908b16ddb9004af5d0 completed April 18, 2026, 7:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0084aa47408190abe2ffaab84cdd85 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:13 a.m.