Triple
T13469038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essen |
E311580
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Emscher |
E524728
|
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: Emscher | Statement: [Essen, river, Emscher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emscher Context triple: [Essen, river, Emscher]
-
A.
Emscher
chosen
The Emscher is a river in Germany’s Ruhr industrial region, historically known for its heavy pollution and extensive canalization before major ecological restoration efforts.
-
B.
Ruhr
The Ruhr is a river in western Germany that flows through the Ruhr industrial region before joining the Rhine.
-
C.
Lippe
The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
-
D.
Lippe
Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
-
E.
Emsdetten
Emsdetten is a town in the district of Steinfurt in North Rhine-Westphalia, Germany, known for its textile industry heritage and location along the Ems 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec869957481909ea4fded01851b70 |
completed | May 9, 2026, 5:38 a.m. |
Created at: April 9, 2026, 9:42 p.m.