Triple
T14578715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumecklenburg |
E342127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former German colonial name |
C22842
|
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 German colonial name Context triple: [Neumecklenburg, instanceOf, former German colonial name]
-
A.
former German colony
A former German colony is a territory that was once under the political control and administration of the German Empire or later German states, but has since gained independence or come under another sovereignty.
-
B.
former German name of a town
chosen
A former German name of a town is a historical place-name once used in the German language for a specific settlement, typically replaced after political, territorial, or cultural changes.
-
C.
Prussian colony
A Prussian colony is a territory politically and administratively controlled by the Kingdom of Prussia, typically acquired through conquest, diplomacy, or settlement, and governed to serve Prussian strategic, economic, and cultural interests.
-
D.
former Dutch colony
A former Dutch colony is a territory that was once governed, administered, or significantly controlled by the Netherlands as part of its overseas colonial empire, but has since gained independence or been transferred to another sovereignty.
-
E.
Dutch colonial territory
A Dutch colonial territory is a region outside Europe that was politically and economically controlled and administered by the Netherlands as part of its overseas empire.
- F. None of above.
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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:24 a.m.