Triple
T12129223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht |
E288888
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Kromme Rijn |
E81826
|
NE FINISHED |
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: Kromme Rijn | Statement: [Utrecht, hasRiver, Kromme Rijn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kromme Rijn Context triple: [Utrecht, hasRiver, Kromme Rijn]
-
A.
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.
-
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.
Geul River
The Geul River is a small, winding river in the southeastern Netherlands and eastern Belgium, known for its scenic valleys, historic watermills, and role in shaping the hilly landscape of South Limburg.
-
D.
Rijn
chosen
Rijn is the Dutch name for the major European river known in English as the Rhine.
-
E.
Oude Maas
The Oude Maas is a major distributary river in the western Netherlands that forms part of the complex Rhine–Meuse–Scheldt delta system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158a2c2c8190aaff9d0cce177565 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6717defe48190bc63b83e2c276ebc |
completed | May 2, 2026, 9:49 p.m. |
Created at: April 8, 2026, 9:49 p.m.