Triple
T4283892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molenlanden |
E97218
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Nieuwpoort |
E130261
|
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: Nieuwpoort | Statement: [Molenlanden, hasSettlement, Nieuwpoort]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nieuwpoort Context triple: [Molenlanden, hasSettlement, Nieuwpoort]
-
A.
Nieuwpoort
chosen
Nieuwpoort is a coastal town in West Flanders, Belgium, known for its historic harbor and its strategic role in World War I.
-
B.
Wilhelmshaven
Wilhelmshaven is a coastal city in northwestern Germany known for its major naval base and port on the North Sea.
-
C.
Terneuzen port
Terneuzen port is a major Dutch seaport and industrial hub on the Western Scheldt, known for its role in maritime trade and access to the Ghent–Terneuzen Canal.
-
D.
Holland-on-Sea
Holland-on-Sea is a coastal town in Essex, England, known for its quiet residential character and sandy beaches along the North Sea.
-
E.
Hampoort
Hampoort is a historic city gate, likely part of the old fortifications of a European town or city.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503c062c81908f9a9eeab5381ec9 |
completed | March 12, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b7c2023c8190a2359f8cabcecd2c |
completed | March 14, 2026, 7:32 p.m. |
Created at: March 12, 2026, 11:07 p.m.