Triple

T12566806
Position Surface form Disambiguated ID Type / Status
Subject Province of Westphalia E295497 entity
Predicate containsSettlement P847 FINISHED
Object Arnsberg E359488 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: Arnsberg | Statement: [Province of Westphalia, containsSettlement, Arnsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arnsberg
Context triple: [Province of Westphalia, containsSettlement, Arnsberg]
  • A. Arnsberg chosen
    Arnsberg is a historic town in the Sauerland region of North Rhine-Westphalia, Germany, known for its medieval old town and surrounding forested hills.
  • 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. Nienburg
    Nienburg is a historic town in Lower Saxony, Germany, known for its medieval architecture and scenic location along the Weser River.
  • 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. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d954a325948190994bcfc9d571a3a8 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79418e26c819088f3aa608d9d65d6 completed May 3, 2026, 6:29 p.m.
Created at: April 8, 2026, 11:49 p.m.