Triple
T3413383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noord-Beveland |
E71951
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Colijnsplaat |
E415610
|
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: Colijnsplaat | Statement: [Noord-Beveland, hasPart, Colijnsplaat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Colijnsplaat Context triple: [Noord-Beveland, hasPart, Colijnsplaat]
-
A.
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.
-
B.
Hulst
Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
-
C.
Scharendijke
chosen
Scharendijke is a village in the Dutch province of Zeeland, known as a popular base for water sports and diving in the Grevelingen and North Sea area.
-
D.
Oudeschild
Oudeschild is a small fishing village and harbor on the Dutch island of Texel, known for its maritime heritage and coastal tourism.
-
E.
Papendrecht
Papendrecht is a Dutch town situated on the river Merwede in the province of South Holland, known for its residential character and proximity to 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb90ba83c81909abdcddb334e64f6 |
completed | March 8, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74208348c819080d1b4432ff617c0 |
completed | March 28, 2026, 2:50 a.m. |
Created at: March 8, 2026, 3:15 p.m.