Triple
T16704692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nedersticht |
E405935
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Oversticht |
E91241
|
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: Oversticht | Statement: [Nedersticht, borderedBy, Oversticht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oversticht Context triple: [Nedersticht, borderedBy, Oversticht]
-
A.
Oversticht
chosen
Oversticht was a medieval territorial region in the northern Low Countries that roughly corresponds to much of the modern Dutch province of Overijssel and surrounding areas.
-
B.
Overbruch
Overbruch is a district within the Walsum borough of Duisburg in North Rhine-Westphalia, Germany.
-
C.
Den Oever
Den Oever is a village in the Dutch province of North Holland, known as a fishing port and gateway to the Afsluitdijk on the former island of Wieringen.
-
D.
De Akkers
De Akkers is a metro station in Spijkenisse, Netherlands, serving as a terminus on the Rotterdam Metro network.
-
E.
De Oversteek
De Oversteek is a modern road bridge over the River Waal in Nijmegen, the Netherlands, commemorating a historic World War II river crossing.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3833496dc8190ae4b4a03ba04d69d |
completed | April 18, 2026, 1:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb04c1e88190b6c9f43fbdfd6bc4 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:19 a.m.