Triple
T17856974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouwe |
E445963
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Oude Rijn |
—
|
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: Oude Rijn | Statement: [Gouwe, connects, Oude Rijn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oude Rijn Context triple: [Gouwe, connects, Oude Rijn]
-
A.
Oude Rijn
chosen
Oude Rijn is a river in the western Netherlands that forms one of the main northern distributaries of the Rhine, flowing through towns such as Leiden before reaching the North Sea.
-
B.
Vaartsche Rijn
Vaartsche Rijn is a historic canal in the Dutch province of Utrecht that connects the city of Utrecht with the Lower Rhine and forms part of its inland waterway network.
-
C.
Nieuwe Rijn
Nieuwe Rijn is a canal and street in the historic center of Leiden, Netherlands, known for its picturesque quays, markets, and traditional Dutch canal-side architecture.
-
D.
Kromme Rijn
Kromme Rijn is a historic branch of the Rhine River in the Dutch province of Utrecht, known for its scenic landscapes and role in regional water management and navigation.
-
E.
Rijn
Rijn is the Dutch name for the major European river known in English as the Rhine.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978d05708190838386d37eb157bc |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:17 a.m.