Triple

T1871519
Position Surface form Disambiguated ID Type / Status
Subject OKH E39045 entity
Predicate headquartersLocation P62 FINISHED
Object Wünsdorf E119154 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: Wünsdorf | Statement: [OKH, headquartersLocation, Wünsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wünsdorf
Context triple: [OKH, headquartersLocation, Wünsdorf]
  • A. Wünsdorf chosen
    Wünsdorf is a town in Brandenburg, Germany, historically notable as a major military garrison and command center, including serving as the site of the German Wehrmacht’s high command during World War II.
  • B. Hermsdorf
    Hermsdorf is a residential locality in the Berlin borough of Reinickendorf, known for its green surroundings and village-like character on the city’s northern edge.
  • C. Hennigsdorf
    Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
  • D. Burkhardtsdorf
    Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern Germany.
  • E. Hubersdorf
    Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
  • 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_69a8862f7074819096afe7fe65e179e9 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb0ba90e08190b990875d6e8e7e4a completed March 7, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae6522bb448190ae50a476da53fcda completed March 9, 2026, 6:13 a.m.
Created at: March 4, 2026, 7:34 p.m.