Triple
T21094185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wijk bij Duurstede |
E519716
|
entity |
| Predicate | hasHistoricName |
P2834
|
FINISHED |
| Object | Dorestad |
—
|
NE NERFINISHED |
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: Dorestad | Statement: [Wijk bij Duurstede, hasHistoricName, Dorestad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dorestad Context triple: [Wijk bij Duurstede, hasHistoricName, Dorestad]
-
A.
Dorestad
chosen
Dorestad was a major early medieval Frisian-Frankish trading center and port on the Rhine, which flourished between the 7th and 9th centuries in what is now the Netherlands.
-
B.
Dieburg
Dieburg is a small historic town in the German state of Hesse, known for its medieval old town and regional administrative role.
-
C.
Stitswerd
Stitswerd is a small village in the northern Netherlands, located in the province of Groningen.
-
D.
Deventer
Deventer is a historic Dutch city known for its medieval architecture, Hanseatic trading past, and annual book market.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e709517a18819081ede1d38e2c4391 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.