Triple
T11913483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian Gold Coast |
E283452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian colony |
C30608
|
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: Prussian colony Context triple: [Prussian Gold Coast, instanceOf, Prussian colony]
-
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.
German protectorate
A German protectorate is a territory formally under the sovereignty of a local ruler or existing state but effectively controlled, administered, and defended by the German Empire or later German state through a treaty-based protectorate arrangement.
-
C.
province of Prussia
A province of Prussia was a major administrative territorial unit within the Kingdom (and later state) of Prussia, serving as a top-level regional division for governance, law, and administration.
-
D.
province of Prussia
A province of Prussia was a major administrative and territorial division within the Kingdom (and later Free State) of Prussia, functioning as a regional unit of government with its own local authorities under the broader Prussian state.
-
E.
constituent state of the German Empire
A constituent state of the German Empire was one of the semi-autonomous kingdoms, grand duchies, duchies, principalities, free Hanseatic cities, or imperial territories that together formed the federal structure of the German Empire from 1871 to 1918.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.