Triple
T30108549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Daciae Ripensis |
E765197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial military governor |
C25583
|
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: provincial military governor Context triple: [dux Daciae Ripensis, instanceOf, provincial military governor]
-
A.
executive head of province
The executive head of province is the highest-ranking official responsible for leading the provincial government, implementing laws and policies, and overseeing administration within the province.
-
B.
imperial governor
An imperial governor is a high-ranking official appointed by a central empire to administer, oversee, and enforce its authority, laws, and policies within a specific province or territory.
-
C.
colonial commander
A colonial commander is a military leader responsible for overseeing, directing, and maintaining control over armed forces and local governance within a colony on behalf of an imperial power.
-
D.
governor of a Roman province
chosen
A governor of a Roman province was an appointed official, often of senatorial or equestrian rank, responsible for administering justice, collecting taxes, commanding military forces, and maintaining order within a defined territorial unit of the Roman state.
-
E.
Ottoman provincial governors
Ottoman provincial governors were imperial officials appointed by the sultan to administer provinces, collect taxes, maintain order, and implement central policies while balancing local power structures within the Ottoman Empire.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:10 p.m.