Triple
T5096565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollands Diep |
E114879
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Moerdijk |
E360196
|
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: Moerdijk | Statement: [Hollands Diep, near, Moerdijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moerdijk Context triple: [Hollands Diep, near, Moerdijk]
-
A.
Moerdijk
chosen
Moerdijk is a municipality and industrial port area in the southern Netherlands, known for its large logistics and chemical industry complexes.
-
B.
Hoogeveen
Hoogeveen is a town and municipality in the northeastern Netherlands known for its historical peat colonies and location in the province of Drenthe.
-
C.
Hoorn
Hoorn is a historic port city in the Netherlands known for its role in the Dutch Golden Age and as a former base of the Dutch East India Company.
-
D.
Groningen
Groningen is a historic province in the northern Netherlands, known for its university city of the same name, flat landscapes, and rich maritime and agricultural heritage.
-
E.
Zwolle
Zwolle is a historic Dutch city in the eastern Netherlands known for its medieval center, cultural heritage, and regional economic importance.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75652a8081908386718f1fdb1de3 |
completed | March 20, 2026, 4:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07d466cbc8190a91dcc0c26aba817 |
completed | March 22, 2026, 11:37 p.m. |
Created at: March 20, 2026, 1:40 p.m.