Triple
T18195798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Tholen |
E435657
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Poortvliet |
—
|
NE NERFINISHED |
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: Poortvliet | Statement: [municipality of Tholen, contains, Poortvliet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poortvliet Context triple: [municipality of Tholen, contains, Poortvliet]
-
A.
Poortvliet
chosen
Poortvliet is a village in the Dutch province of Zeeland, located on the island of Tholen.
-
B.
Onderdendam
Onderdendam is a small historic village in the Dutch province of Groningen, known for its canals, bridges, and traditional architecture.
-
C.
Blokhuispoort
Blokhuispoort is a former prison complex in Leeuwarden, Netherlands, that has been transformed into a cultural and creative hub with museums, studios, and public spaces.
-
D.
Santpoort
Santpoort is a village in the Dutch province of North Holland, known for its historic estates, dunes, and proximity to the city of Haarlem.
-
E.
Oostersluis
Oostersluis is a lock complex in the Dutch city of Groningen that regulates water levels and vessel traffic on the Van Starkenborghkanaal.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d2ad5881909d846f3851ac9ec9 |
completed | April 19, 2026, 2:04 p.m. |
Created at: April 10, 2026, 10:31 a.m.