Triple
T7547751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diksmuide |
E178449
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Yser |
E164297
|
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: Yser | Statement: [Diksmuide, river, Yser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yser Context triple: [Diksmuide, river, Yser]
-
A.
Yser River
chosen
The Yser River is a short coastal river in northern France and western Belgium that flows into the North Sea and is historically notable for its role in World War I.
-
B.
Yser basin
The Yser basin is the catchment area in northern France and western Belgium that collects and channels water flowing into the Yser River before it reaches the North Sea.
-
C.
Sambre
The Sambre is a major river in northern France and southern Belgium that flows through the Walloon region before joining the Meuse at Namur.
-
D.
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.
-
E.
River Zenne
The River Zenne is a small Belgian river that flows through Brussels and surrounding towns, historically shaping the region’s development and urban landscape.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89a7b2c8190b2ca57edbb4f0390 |
completed | March 27, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84f2b0de48190a854b4d4935c2254 |
completed | March 28, 2026, 9:59 p.m. |
Created at: March 27, 2026, 3:49 p.m.