Triple
T11522172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margraviate of Brandenburg-Ansbach |
E273191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial state |
C9452
|
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: imperial state Context triple: [Margraviate of Brandenburg-Ansbach, instanceOf, imperial state]
-
A.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
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.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
D.
dynastic empire
A dynastic empire is a vast, centralized state ruled over generations by a single family lineage that legitimizes its authority through hereditary succession and often divine or traditional claims to power.
-
E.
imperial state of the Holy Roman Empire
chosen
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.