Triple
T13563794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zutphen |
E323979
|
entity |
| Predicate | regionalDialect |
P1762
|
FINISHED |
| Object | Achterhoeks |
E14290
|
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: Achterhoeks | Statement: [Zutphen, regionalDialect, Achterhoeks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Achterhoeks Context triple: [Zutphen, regionalDialect, Achterhoeks]
-
A.
Achterhooks
chosen
Achterhooks is a regional Low Saxon dialect spoken in the Achterhoek area of the eastern Netherlands.
-
B.
Overhoeks
Overhoeks is a modern waterfront district in Amsterdam known for its contemporary architecture, cultural venues, and redevelopment of former industrial land along the IJ river.
-
C.
De Akkers
De Akkers is a metro station in Spijkenisse, Netherlands, serving as a terminus on the Rotterdam Metro network.
-
D.
Oudezijde
Oudezijde is a historic quarter in Amsterdam’s medieval city center, known for its canals, old churches, and traditional urban fabric.
-
E.
Heenweg
Heenweg is a small village in the Dutch municipality of Westland in the province of South Holland, 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75daf1bfc8190bf22eb9ef242f54f |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.