Triple
T15423815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwelm |
E369451
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Ennepe |
E531916
|
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: Ennepe | Statement: [Schwelm, hasRiver, Ennepe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ennepe Context triple: [Schwelm, hasRiver, Ennepe]
-
A.
Ennepe
chosen
Ennepe is a river in North Rhine-Westphalia, Germany, that flows through the town of Ennepetal and serves as a tributary of the Ruhr.
-
B.
Ahr River
The Ahr River is a tributary of the Rhine in western Germany, known for flowing through the Eifel region and its surrounding wine-growing valleys.
-
C.
Enkenbach
Enkenbach is a locality in the German state of Rhineland-Palatinate, situated near Kaiserslautern and served by regional rail connections.
-
D.
Elbbach
Elbbach is a river in western Germany that flows through the town of Hadamar and is a tributary of the Lahn River.
-
E.
Aschaff River
The Aschaff River is a small river in Bavaria, Germany, that flows through the Spessart region before joining the Main River.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb593258081909dcaf2b37fd28e63 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 3:20 a.m.