Triple
T22016074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiden region |
E543711
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Nieuwe 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: Nieuwe Rijn | Statement: [Leiden region, hasRiver, Nieuwe Rijn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nieuwe Rijn Context triple: [Leiden region, hasRiver, Nieuwe Rijn]
-
A.
Nieuwe Rijn
chosen
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.
-
B.
Oude Rijn
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.
-
C.
Nederrijn
The Nederrijn is a major distributary branch of the Rhine River in the Netherlands, flowing through cities such as Arnhem and forming an important part of the Dutch river system.
-
D.
Rijn
Rijn is the Dutch name for the major European river known in English as the Rhine.
-
E.
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.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a8a1388190b9e0c1795fe1183a |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:22 p.m.