Triple
T30680128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodian tetrarchy |
E781029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman client system |
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: Roman client system Context triple: [Herodian tetrarchy, instanceOf, Roman client system]
-
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 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.
-
D.
Byzantine client state
A Byzantine client state was a formally independent but subordinate polity that relied on the Byzantine Empire for protection, guidance, and often tribute, while serving its strategic, political, or diplomatic interests.
-
E.
Roman citizen
A Roman citizen is an individual legally recognized as a member of the Roman state, endowed with specific rights, protections, and civic responsibilities under Roman law.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.