Triple
T13544046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lopik |
E323465
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | river Lek |
E356286
|
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: river Lek | Statement: [Lopik, locatedOn, river Lek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: river Lek Context triple: [Lopik, locatedOn, river Lek]
-
A.
River Lek
chosen
River Lek is a major distributary branch of the Rhine in the central Netherlands, flowing through the provinces of Utrecht and South Holland and playing an important role in regional shipping and water management.
-
B.
River Leri
River Leri is a small river in Ceredigion, Wales, that flows from the Pumlumon massif to the Cardigan Bay coast near Borth.
-
C.
Lasne River
The Lasne River is a small watercourse in central Belgium that flows through the Walloon Brabant region before joining the Dyle River.
-
D.
Lom River
The Lom River is a waterway in central Cameroon that contributes to the Sanaga River system and supports surrounding ecosystems and local communities.
-
E.
Leko River
The Leko River is a waterway in South Sumatra, Indonesia, that forms part of the Musi River basin and contributes to the region’s extensive river network.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafda36248190acabde65a88c5471 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da094288190aff108b006c3da1f |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.