Triple

T722056
Position Surface form Disambiguated ID Type / Status
Subject Werl Prison E14637 entity
Predicate locatedNear P294 FINISHED
Object 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: Dortmund | Statement: [Werl Prison, locatedNear, Dortmund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dortmund
Context triple: [Werl Prison, locatedNear, 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. Düsseldorf
    Düsseldorf is a major German city on the Rhine River known for its fashion and art scenes, modern architecture, and status as an important economic and financial center.
  • C. Duisburg
    Duisburg is a major industrial and port city in western Germany’s Ruhr region, known for its steel production and one of the world’s largest inland harbors.
  • D. Wolfsburg
    Wolfsburg is a German city best known as the headquarters and main production site of the Volkswagen automobile company.
  • E. Gelsenkirchen
    Gelsenkirchen is a city in western Germany known for its strong football culture and modern stadium, Veltins-Arena, home to FC Schalke 04.
  • 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_69a4934c753c81909b309027e48b9b3a completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a591124c8190842e7ef18b064198 completed March 1, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69aea8034cf0819089240d70f0a346a6 completed March 9, 2026, 10:59 a.m.
Created at: March 1, 2026, 7:37 p.m.