Triple
T4055155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twents |
E84675
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Oldenzaals |
E242770
|
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: Oldenzaals | Statement: [Twents, hasDialect, Oldenzaals]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oldenzaals Context triple: [Twents, hasDialect, Oldenzaals]
-
A.
Oldenzaal
chosen
Oldenzaal is a historic city in the eastern Netherlands known for its medieval center and location near the German border in the province of Overijssel.
-
B.
Oldehove
Oldehove is a village in the Dutch province of Groningen, known for its rural character and historic church.
-
C.
Elsenz
The Elsenz is a river in southwestern Germany that flows through the Kraichgau region before joining the Neckar.
-
D.
Goudswaard
Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
-
E.
Nieuwolda
Nieuwolda is a small village in the municipality of Oldambt 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562a0f19c819084d23c3802ce8ca6 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.