Triple

T6155486
Position Surface form Disambiguated ID Type / Status
Subject Bad Godesberg E137309 entity
Predicate hasSubdistrict P747 FINISHED
Object Plittersdorf unclear NED1 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: Plittersdorf | Statement: [Bad Godesberg, hasSubdistrict, Plittersdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Plittersdorf
Context triple: [Bad Godesberg, hasSubdistrict, Plittersdorf]
  • A. Plittersdorf
    Plittersdorf is a village and district of the town of Rastatt in the state of Baden-Württemberg in southwestern Germany.
  • B. Lengsdorf
    Lengsdorf is a district of the Bonn borough of Hardtberg in Germany, known for its residential character and proximity to both urban amenities and surrounding green areas.
  • C. Hubersdorf
    Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
  • D. Burkhardtsdorf
    Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern Germany.
  • E. Wintersdorf
    Wintersdorf is a village and district of the town of Rastatt in the state of Baden-Württemberg in southwestern Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69c008a45d008190832a9e19f5d63406 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d01ddb0819085b5f5338b86a25d completed March 22, 2026, 9:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65fadf36c819091b57c2c390f72b5 completed March 27, 2026, 10:45 a.m.
Created at: March 22, 2026, 4:17 p.m.