Triple
T1624737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Leipzig |
E35114
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object |
River Mulde
The River Mulde is a river in central Germany that flows through the states of Saxony and Saxony-Anhalt before joining the Elbe.
|
E235278
|
NE FINISHED |
How this triple was built (4 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: River Mulde | Statement: [District of Leipzig, traversedBy, River Mulde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Mulde Context triple: [District of Leipzig, traversedBy, River Mulde]
-
A.
Chemnitz River
The Chemnitz River is a waterway in the German state of Saxony that flows through and gives its name to the city of Chemnitz.
-
B.
River Spree
River Spree is a major river flowing through Berlin, Germany, known for shaping the city’s landscape and passing many historic and cultural landmarks.
-
C.
Dahme
The Dahme is a river in eastern Germany that flows through Brandenburg and Berlin before joining the Spree.
-
D.
Saale
The Saale is a major river in central Germany that flows through the states of Thuringia, Saxony-Anhalt, and Bavaria before joining the Elbe.
-
E.
Inn River
The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: River Mulde Triple: [District of Leipzig, traversedBy, River Mulde]
Generated description
The River Mulde is a river in central Germany that flows through the states of Saxony and Saxony-Anhalt before joining the Elbe.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: River Mulde Target entity description: The River Mulde is a river in central Germany that flows through the states of Saxony and Saxony-Anhalt before joining the Elbe.
-
A.
Chemnitz River
The Chemnitz River is a waterway in the German state of Saxony that flows through and gives its name to the city of Chemnitz.
-
B.
River Spree
River Spree is a major river flowing through Berlin, Germany, known for shaping the city’s landscape and passing many historic and cultural landmarks.
-
C.
Dahme
The Dahme is a river in eastern Germany that flows through Brandenburg and Berlin before joining the Spree.
-
D.
Saale
The Saale is a major river in central Germany that flows through the states of Thuringia, Saxony-Anhalt, and Bavaria before joining the Elbe.
-
E.
Inn River
The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
- F. None of above. chosen
Provenance (5 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909d19b008190b2224717b2909a78 |
completed | March 5, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae303cdce081909b66ec04de43cf53 |
completed | March 9, 2026, 2:28 a.m. |
| NEDg | Description generation | batch_69ae31549dec8190b3c9e8a73d561334 |
completed | March 9, 2026, 2:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae32673a948190bd2bc136edc33344 |
completed | March 9, 2026, 2:37 a.m. |
Created at: March 4, 2026, 7:28 p.m.