Triple
T10838408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostersluis |
E255820
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Oostersluis (nl) |
E255820
|
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: Oostersluis (nl) | Statement: [Oostersluis, hasNameInLanguage, Oostersluis (nl)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oostersluis (nl) Context triple: [Oostersluis, hasNameInLanguage, Oostersluis (nl)]
-
A.
Oostersluis
chosen
Oostersluis is a lock complex in the Dutch city of Groningen that regulates water levels and vessel traffic on the Van Starkenborghkanaal.
-
B.
Oranjesluizen
Oranjesluizen is a complex of navigation locks and water management structures in Amsterdam that regulates water levels and access between the IJ/Markermeer and the city’s waterways.
-
C.
Sluis
Sluis is a historic municipality and town in the southwestern Dutch province of Zeeland, near the Belgian border.
-
D.
Torensluis
Torensluis is one of Amsterdam’s oldest and widest stone bridges, notable for its historic architecture and remnants of a former tower and prison cells.
-
E.
Oosterhoek
Oosterhoek is a historical region in the province of Groningen in the northeastern Netherlands.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d747002b3081908726901ee83d8f38 |
completed | April 9, 2026, 6:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb139072081908a67e76a83575c32 |
completed | April 14, 2026, 9:27 p.m. |
Created at: April 8, 2026, 9:19 p.m.