Triple
T5357165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchy of Finland |
E102723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constituent part of an empire |
C18002
|
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: constituent part of an empire Context triple: [Grand Duchy of Finland, instanceOf, constituent part of an empire]
-
A.
part of the Ottoman Empire
A "part of the Ottoman Empire" is a territorial, administrative, or political subdivision that was under the sovereignty and governance of the Ottoman state during its existence.
-
B.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
C.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
-
D.
colonial empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
-
E.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.