Triple
T10052263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Dordrecht |
E208774
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Papendrecht |
E188862
|
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: Papendrecht | Statement: [Port of Dordrecht, nearbyCity, Papendrecht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Papendrecht Context triple: [Port of Dordrecht, nearbyCity, Papendrecht]
-
A.
Papendrecht
chosen
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.
-
B.
Valkenswaard
Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
-
C.
Apeldoorn
Apeldoorn is a city in the province of Gelderland in the Netherlands, known for the royal palace Het Loo and its historical ties to the Dutch monarchy.
-
D.
Hulst
Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
-
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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9135bc8190a48a2e5cbafca0cd |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65e9136bc8190b35685376da7007e |
completed | May 2, 2026, 8:29 p.m. |
Created at: March 30, 2026, 8:56 p.m.