Triple
T32028916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcomannic kingdom in Bohemia |
E817894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | barbarian client kingdom of Rome |
C9381
|
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: barbarian client kingdom of Rome Context triple: [Marcomannic kingdom in Bohemia, instanceOf, barbarian client kingdom of Rome]
-
A.
client state of the Roman Empire
chosen
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
-
B.
client state of the Roman Republic
A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
-
C.
Roman regio
A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
-
D.
Roman client ruler
A Roman client ruler was a local king or chieftain who retained nominal authority over their territory while governing under the supervision and in the interests of the Roman Empire.
-
E.
King of Rome
The King of Rome is a conceptual class representing the sovereign ruler of the ancient Roman Kingdom, embodying supreme political, religious, and military authority prior to the establishment of the Roman Republic.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:17 a.m.