Triple
T3499212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Scheldt |
E73923
|
entity |
| Predicate | flowsPast |
P4996
|
FINISHED |
| Object | Hansweert |
E640041
|
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: Hansweert | Statement: [Western Scheldt, flowsPast, Hansweert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hansweert Context triple: [Western Scheldt, flowsPast, Hansweert]
-
A.
Hansweert
chosen
Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
-
B.
Deurne
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
C.
Yerseke
Yerseke is a Dutch village in the province of Zeeland, best known for its mussel and oyster farming along the Eastern Scheldt.
-
D.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
-
E.
Zwijndrecht
Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd3ad548190abbfae820bf3b66d |
completed | March 8, 2026, 6:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1c351f848190a1f91a09f7319a01 |
completed | April 2, 2026, 7:35 a.m. |
Created at: March 8, 2026, 3:18 p.m.