Triple
T817690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield |
E17685
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Bochum |
E248839
|
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: Bochum | Statement: [Sheffield, twinTown, Bochum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bochum Context triple: [Sheffield, twinTown, Bochum]
-
A.
Bochum
chosen
Bochum is a major city in Germany’s Ruhr region known for its industrial heritage, cultural institutions, and large university.
-
B.
Gelsenkirchen
Gelsenkirchen is a city in western Germany known for its strong football culture and modern stadium, Veltins-Arena, home to FC Schalke 04.
-
C.
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.
-
D.
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.
-
E.
Bielefeld
Bielefeld is a major city in northwestern Germany known for its industrial heritage, university, and the tongue-in-cheek “Bielefeld conspiracy” meme claiming it does not exist.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab63f4a48190a61a14c3c41ed641 |
completed | March 1, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af8309912c819096cf0dad7039ec95 |
completed | March 10, 2026, 2:33 a.m. |
Created at: March 1, 2026, 7:38 p.m.