Triple

T10078333
Position Surface form Disambiguated ID Type / Status
Subject Wessum E213830 entity
Predicate hasMunicipalAuthority P3379 FINISHED
Object Stadt Ahaus E691013 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: Stadt Ahaus | Statement: [Wessum, hasMunicipalAuthority, Stadt Ahaus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stadt Ahaus
Context triple: [Wessum, hasMunicipalAuthority, Stadt Ahaus]
  • A. Stadt Ahaus chosen
    Stadt Ahaus is a town in the district of Borken in North Rhine-Westphalia, Germany, known for its historic castle and proximity to the Dutch border.
  • B. Meppen
    Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
  • C. Dülmen
    Dülmen is a town in western Germany’s North Rhine-Westphalia, known for its location between Münster and the Ruhr area and for the wild Dülmen ponies in the nearby nature reserve.
  • D. Dorsten
    Dorsten is a town in North Rhine-Westphalia, Germany, located in the Ruhr area and known for its mix of industrial heritage and nearby natural landscapes.
  • E. Bentheim
    Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
  • 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_69ca839bf730819086900c323c9b8c95 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd030a0fc819084b523e8e63636fa completed April 2, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d96b0e4eac8190af28db3d334852cb completed April 10, 2026, 9:26 p.m.
Created at: March 30, 2026, 9 p.m.