Triple

T3874813
Position Surface form Disambiguated ID Type / Status
Subject Arnsberg region E92473 entity
Predicate contains P35 FINISHED
Object city of Dortmund E162155 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: city of Dortmund | Statement: [Arnsberg region, contains, city of Dortmund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Dortmund
Context triple: [Arnsberg region, contains, city of Dortmund]
  • A. Dortmund chosen
    Dortmund is a major city in western Germany known for its rich football culture, industrial heritage, and home club Borussia Dortmund.
  • B. Mönchengladbach
    Mönchengladbach is a city in western Germany known for its textile industry heritage and its football club Borussia Mönchengladbach.
  • C. Gelsenkirchen
    Gelsenkirchen is a city in western Germany known for its strong football culture and modern stadium, Veltins-Arena, home to FC Schalke 04.
  • D. Mülheim an der Ruhr
    Mülheim an der Ruhr is a city in western Germany’s Ruhr area, known for its industrial heritage, riverside setting on the Ruhr River, and role as a regional economic and cultural center.
  • E. Recklinghausen
    Recklinghausen is a city in the Ruhr area of North Rhine-Westphalia, western Germany, known historically for coal mining and its role as a regional administrative center.
  • 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_69aed967448c819086c4b358d37b25aa completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec59bea08190b1e193f34944a2ee completed March 9, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c87214881908e03f5c770c58713 completed March 14, 2026, 8:29 a.m.
Created at: March 9, 2026, 3:20 p.m.