Triple
T17824716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyle River |
E445083
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Lasne 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: Lasne River | Statement: [Dyle River, hasTributary, Lasne River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lasne River Context triple: [Dyle River, hasTributary, Lasne River]
-
A.
Lasne River
chosen
The Lasne River is a small watercourse in central Belgium that flows through the Walloon Brabant region before joining the Dyle River.
-
B.
Lorze River
The Lorze River is a Swiss river in the canton of Zug, known for flowing through the Ägeri Valley and the Höllgrotten caves before joining the Reuss.
-
C.
Lyp River
The Lyp River is a watercourse that serves as a right-bank tributary within the Siva River drainage system.
-
D.
Arpath River
Arpath River is a mountain river in the Anantnag district of Jammu and Kashmir, India, known for its cold, clear waters fed by Himalayan glaciers and springs.
-
E.
Ognon River
The Ognon River is a waterway in eastern France that flows through the Bourgogne-Franche-Comté region before joining the Saône River.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4891352ac8190ad3d669fea1c9fbb |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.