Triple
T22413927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maasdriel |
E554062
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Lingewaal |
E542877
|
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: Lingewaal | Statement: [Maasdriel, hasBorderWith, Lingewaal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lingewaal Context triple: [Maasdriel, hasBorderWith, Lingewaal]
-
A.
Lingewaal
chosen
Lingewaal was a former municipality in the Dutch province of Gelderland, known for encompassing several rural villages along the river Linge.
-
B.
Lingewaard
Lingewaard is a municipality in the Dutch province of Gelderland, situated in the Betuwe region between the cities of Arnhem and Nijmegen.
-
C.
Elingaard
Elingaard is a historic estate and former manor located in the municipality of Rygge in southeastern Norway.
-
D.
Zwanenburg
Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
-
E.
Langerak
Langerak is a small village in the Dutch province of South Holland, known for its rural character and location along the Lek River.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15945486081908eb3a7b0441c0ef1 |
completed | April 29, 2026, 1:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b0c64c5d08190a8e762453874afb0 |
completed | May 18, 2026, 12:56 p.m. |
Created at: April 16, 2026, 8:46 p.m.