Triple

T9498736
Position Surface form Disambiguated ID Type / Status
Subject Neustadt an der Waldnaab (district) E229079 entity
Predicate contains P35 FINISHED
Object Waidhaus E433939 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: Waidhaus | Statement: [Neustadt an der Waldnaab (district), contains, Waidhaus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waidhaus
Context triple: [Neustadt an der Waldnaab (district), contains, Waidhaus]
  • A. Waidhaus chosen
    Waidhaus is a municipality in eastern Bavaria, Germany, near the Czech border, known as a key road border crossing and transport hub.
  • B. Hausen
    Hausen is a small suburban district of the town of Herbrechtingen in the state of Baden-Württemberg, Germany.
  • C. Wildhaus
    Wildhaus is a village in the Swiss canton of St. Gallen, known as the alpine birthplace of Protestant reformer Huldrych Zwingli.
  • D. Almenhof
    Almenhof is a residential district of Mannheim in the German state of Baden-Württemberg.
  • E. Woermannhaus
    Woermannhaus is a historic German colonial-era building in Swakopmund, Namibia, known for its distinctive architecture and prominent tower.
  • 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_69ca84753660819098e8d416e89e26ae completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd983a94c48190a7ddf95a953c4ecc completed April 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12d412a008190adc82e1e3d56d107 completed April 4, 2026, 3:24 p.m.
Created at: March 30, 2026, 7:56 p.m.