Triple
T12600359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuppertal Suspension Railway |
E300839
|
entity |
| Predicate | routeEnd |
P390
|
FINISHED |
| Object | Oberbarmen |
E300847
|
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: Oberbarmen | Statement: [Wuppertal Suspension Railway, routeEnd, Oberbarmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberbarmen Context triple: [Wuppertal Suspension Railway, routeEnd, Oberbarmen]
-
A.
Oberbarmen
chosen
Oberbarmen is a district of the German city of Wuppertal, known as an eastern urban area with residential neighborhoods and industrial heritage.
-
B.
Grömitz
Grömitz is a Baltic Sea resort town in northern Germany known for its long sandy beaches and seaside tourism.
-
C.
Geringswalde
Geringswalde is a small town in the Free State of Saxony in eastern Germany, known for its rural character and location within the Central Saxon region.
-
D.
Schkopau
Schkopau is a municipality in the Saalekreis district of Saxony-Anhalt, Germany, known for its large chemical industry complex.
-
E.
Oppeln
Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954d1f6ac8190ab21ca7bcbc80129 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ec92c6c8190bd2d193e70940407 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:09 p.m.