Triple
T14251328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprockhövel |
E353269
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Schwelm |
E369451
|
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: Schwelm | Statement: [Sprockhövel, locatedNear, Schwelm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwelm Context triple: [Sprockhövel, locatedNear, Schwelm]
-
A.
Schwelm
chosen
Schwelm is a small town in North Rhine-Westphalia, Germany, known as the administrative seat of the Ennepe-Ruhr district.
-
B.
Lüdenscheid
Lüdenscheid is a town in western Germany’s Sauerland region, historically noted for its role in World War II and known today for its metal and plastics industries.
-
C.
Meppen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
-
D.
Lüdinghausen
Lüdinghausen is a historic town in western Germany known for its medieval castles and picturesque setting in the Münsterland region.
-
E.
Gummersbach
Gummersbach is a town in North Rhine-Westphalia, Germany, known as a regional center in the Bergisches Land and a location for higher education and industry.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6296f9d0819086f62f525d07eb12 |
completed | April 14, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3ab3c8881909da34dc94a1deff2 |
completed | May 9, 2026, 11:30 p.m. |
Created at: April 10, 2026, 1:08 a.m.