Triple
T777110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbe |
E16410
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | Mulde |
E78272
|
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: Mulde | Statement: [Elbe, tributary, Mulde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mulde Context triple: [Elbe, tributary, Mulde]
-
A.
Mulde
chosen
The Mulde is a river in central Germany that flows through the state of Saxony and is formed by the confluence of the Zwickauer Mulde and Freiberger Mulde.
-
B.
Inn River
The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
-
C.
Schwabach
Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
-
D.
Pirna
Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
-
E.
Lahn
The Lahn is a river in western Germany that flows through the states of North Rhine-Westphalia, Hesse, and Rhineland-Palatinate before joining the Rhine.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac2a06c99881908c4f44b6bf91db1c |
completed | March 7, 2026, 1:37 p.m. |
Created at: March 1, 2026, 7:37 p.m.