Triple
T16805025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erlecom |
E408457
|
entity |
| Predicate | hasNearbyWaterBody |
P1489
|
FINISHED |
| Object | Waal River |
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 River | Statement: [Erlecom, hasNearbyWaterBody, Waal River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waal River Context triple: [Erlecom, hasNearbyWaterBody, Waal River]
-
A.
Lange river
The Lange river is a small watercourse in eastern France that flows through the town of Oyonnax in the Ain department.
-
B.
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.
-
C.
Grobbelaars River
Grobbelaars River is a watercourse in South Africa’s Western Cape that flows through the town of Oudtshoorn in the semi-arid Little Karoo region.
-
D.
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.
-
E.
Riet River
The Riet River is a watercourse in South Africa that played a notable role as a strategic crossing point during the Second Boer War.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cb68508190a05749bad68f7b43 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c79a96408190ab01ccd144f3fade |
completed | May 10, 2026, 5:59 p.m. |
Created at: April 10, 2026, 5:22 a.m.