Triple
T17052765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ketelmeer |
E413741
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Vossemeer |
E531405
|
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: Vossemeer | Statement: [Ketelmeer, connectedTo, Vossemeer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vossemeer Context triple: [Ketelmeer, connectedTo, Vossemeer]
-
A.
Reimerswaal
Reimerswaal is a coastal municipality in the Dutch province of Zeeland, known for its agricultural landscape and location along the Eastern Scheldt estuary.
-
B.
Ederveen
Ederveen is a village in the Dutch province of Gelderland, known for its rural character and location within the municipality of Ede.
-
C.
Vechta
Vechta is a town in Lower Saxony, Germany, known for its historical significance, university, and annual Stoppelmarkt fair.
-
D.
Eendracht
Eendracht was a prominent 17th-century Dutch warship that served as the flagship of the Dutch fleet during major naval engagements of the Anglo-Dutch Wars.
-
E.
Eendracht
chosen
Eendracht is a waterway in the southwestern Netherlands that forms part of the main shipping route between the Scheldt and Rhine river systems.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa3324881908d9e445ba1cfe109 |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ed60d3481909c8144bcb01316a1 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.