Triple
T20967611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wijk bij Duurstede |
E516409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Hanseatic town |
C44142
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former Hanseatic town Context triple: [Wijk bij Duurstede, instanceOf, former Hanseatic town]
-
A.
former Prussian city
A former Prussian city is an urban settlement that historically belonged to the Kingdom of Prussia or the later Prussian state but now lies within the borders of a different modern nation.
-
B.
former port city
A former port city is an urban settlement that once functioned as a significant maritime trade hub but has since lost its port operations or primary seafaring role due to economic, environmental, or infrastructural changes.
-
C.
historic confederation of towns
A historic confederation of towns is a formal alliance of multiple municipalities that cooperatively coordinate defense, trade, governance, or mutual support while retaining their individual local autonomy.
-
D.
Hanseatic kontor
A Hanseatic kontor was a major overseas trading office and enclave of the Hanseatic League, serving as a commercial, administrative, and diplomatic hub for its merchant communities in foreign cities.
-
E.
former castle town
A former castle town is a settlement that historically developed around and was economically, socially, and administratively centered on a castle, but no longer functions in that original feudal or defensive role.
- F. None of above. chosen
Provenance (1 batch)
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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:37 p.m.