Triple
T4313820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiel |
E94139
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Waal |
E26512
|
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: Waal | Statement: [Tiel, locatedOnRiver, Waal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waal Context triple: [Tiel, locatedOnRiver, Waal]
-
A.
Waal
chosen
The Waal is a major distributary branch of the Rhine River in the Netherlands, serving as an important waterway for shipping and part of the country’s main river system.
-
B.
Geul
The Geul is a small river in the southeastern Netherlands and eastern Belgium, known for flowing through the hilly Limburg landscape and picturesque villages before joining the Meuse.
-
C.
River Waal
River Waal is a major distributary branch of the Rhine in the Netherlands, serving as an important waterway for transport and trade.
-
D.
Beneden Merwede
Beneden Merwede is a major distributary branch of the Rhine–Meuse river system in the western Netherlands, important for inland shipping and regional water management.
-
E.
Rupel
The Rupel is a short river in northern Belgium that flows through the province of Antwerp and joins the Scheldt near the town of Rupelmonde.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f319c08190bb40a9fc5933728d |
completed | March 12, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b65f24783c8190a735629237069a92 |
completed | March 15, 2026, 7:26 a.m. |
Created at: March 12, 2026, 11:12 p.m.