Triple
T1464949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJssel |
E27000
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Deventer |
E360206
|
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: Deventer | Statement: [IJssel, passesThrough, Deventer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deventer Context triple: [IJssel, passesThrough, Deventer]
-
A.
Deventer
chosen
Deventer is a historic Dutch city known for its medieval architecture, Hanseatic trading past, and annual book market.
-
B.
Culemborg
Culemborg is a historic town in the Dutch province of Gelderland, known for its medieval center and role in the early Dutch colonial era.
-
C.
Zutphen
Zutphen is a historic city in the eastern Netherlands known for its well-preserved medieval center and location along the river IJssel.
-
D.
Zwolle
Zwolle is a historic Dutch city in the eastern Netherlands known for its medieval center, cultural heritage, and regional economic importance.
-
E.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5ba2d5c81909ee85713de961fcb |
completed | March 1, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4029cfa148190baad6968cf6dad3a |
completed | March 13, 2026, 12:27 p.m. |
Created at: March 1, 2026, 8:01 p.m.