Triple
T20961081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eder |
E516244
|
entity |
| Predicate | majorTributary |
P415
|
FINISHED |
| Object | Schwalm (river) |
—
|
NE NERFINISHED |
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: Schwalm (river) | Statement: [Eder, majorTributary, Schwalm (river)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwalm (river) Context triple: [Eder, majorTributary, Schwalm (river)]
-
A.
Schwalm River
chosen
The Schwalm River is a waterway in the German state of Hesse that lends its name to the surrounding Schwalm-Eder region.
-
B.
Schwalm (Rur)
Schwalm (Rur) is a river in western Germany that serves as a tributary of the Rur, flowing through North Rhine-Westphalia and the Netherlands.
-
C.
Schwabach River
The Schwabach River is a small river in Bavaria, Germany, that flows through the town of Schwabach before joining the Rednitz River.
-
D.
Emsbach river
The Emsbach river is a small watercourse in the German state of Hesse that flows through towns such as Bad Camberg before joining larger regional river systems.
-
E.
Fulda River
The Fulda River is a major river in central Germany that flows through the state of Hesse and joins the Werra River at Hann. Münden to form the Weser.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6f134081908b1ed48ce708f3d5 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 1:31 p.m.