Triple

T16381244
Position Surface form Disambiguated ID Type / Status
Subject Soest district E397811 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Werl E100762 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: Werl | Statement: [Soest district, containsAdministrativeTerritorialEntity, Werl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Werl
Context triple: [Soest district, containsAdministrativeTerritorialEntity, Werl]
  • A. Werl chosen
    Werl is a town in North Rhine-Westphalia, Germany, known for its historical significance and regional correctional facility.
  • B. Voerde
    Voerde is a town in the Wesel district of North Rhine-Westphalia, Germany, situated on the Lower Rhine in the Ruhr region.
  • 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. Stadshagen
    Stadshagen is a residential and commercial district on the island of Kungsholmen in central Stockholm, Sweden.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319dd0e0c8190812bde6a2f7d9644 completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00457751208190b1e3dd6be3c0f363 completed May 10, 2026, 8:44 a.m.
Created at: April 10, 2026, 5:08 a.m.