Triple
T14125726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wupper basin |
E340025
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Radevormwald |
E203519
|
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: Radevormwald | Statement: [Wupper basin, containsTown, Radevormwald]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Radevormwald Context triple: [Wupper basin, containsTown, Radevormwald]
-
A.
Radevormwald
chosen
Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
-
B.
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.
-
C.
Waldbröl
Waldbröl is a small town in North Rhine-Westphalia, Germany, known for its rural setting in the Bergisches Land region.
-
D.
Wülscheid
Wülscheid is a small locality within the Aegidienberg district of Bad Honnef in North Rhine-Westphalia, Germany.
-
E.
Gescher
Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd1bb1c48190b5d2b4167c756abf |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 9, 2026, 10:22 p.m.