Triple
T1320712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oder River |
E28210
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object |
Neisse River
The Neisse River is a Central European river that forms part of the border between Germany and Poland before joining the Oder River.
|
E240507
|
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: Neisse River | Statement: [Oder River, tributary, Neisse River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neisse River Context triple: [Oder River, tributary, Neisse River]
-
A.
Magadanka River
The Magadanka River is a small river in Russia’s Magadan Oblast that flows through the city of Magadan and gives the city its name.
-
B.
Svir River
The Svir River is a waterway in northwestern Russia that links Lake Onega to Lake Ladoga and forms part of the Volga–Baltic waterway system.
-
C.
Klyazma River
The Klyazma River is a significant waterway in western Russia that flows through several regions, including Moscow Oblast, before joining the Oka River.
-
D.
Tosna River
The Tosna River is a waterway in northwestern Russia that flows through the Leningrad Oblast before joining the Neva River.
-
E.
Vetluga River
The Vetluga River is a significant waterway in western Russia that flows through several regions before joining the Volga River.
- 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: Neisse River Triple: [Oder River, tributary, Neisse River]
Generated description
The Neisse River is a Central European river that forms part of the border between Germany and Poland before joining the Oder River.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Neisse River Target entity description: The Neisse River is a Central European river that forms part of the border between Germany and Poland before joining the Oder River.
-
A.
Magadanka River
The Magadanka River is a small river in Russia’s Magadan Oblast that flows through the city of Magadan and gives the city its name.
-
B.
Svir River
The Svir River is a waterway in northwestern Russia that links Lake Onega to Lake Ladoga and forms part of the Volga–Baltic waterway system.
-
C.
Klyazma River
The Klyazma River is a significant waterway in western Russia that flows through several regions, including Moscow Oblast, before joining the Oka River.
-
D.
Tosna River
The Tosna River is a waterway in northwestern Russia that flows through the Leningrad Oblast before joining the Neva River.
-
E.
Vetluga River
The Vetluga River is a significant waterway in western Russia that flows through several regions before joining the Volga River.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c179883c8190b68fbeebb9696982 |
completed | March 1, 2026, 10:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58a410a8819091c9bc3f46b0c09d |
completed | March 9, 2026, 5:20 a.m. |
| NEDg | Description generation | batch_69ae59a9b010819081491e988184b386 |
completed | March 9, 2026, 5:24 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae5a10607881909849a72201399d62 |
completed | March 9, 2026, 5:26 a.m. |
Created at: March 1, 2026, 7:55 p.m.