Triple
T11794209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vilém Slavata of Chlum |
E280463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial governor |
C29818
|
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 governor Context triple: [Vilém Slavata of Chlum, instanceOf, imperial governor]
-
A.
governor of a Roman province
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.
-
B.
governor-general
A governor-general is the representative of a monarch in a constitutional monarchy, performing ceremonial duties and certain constitutional functions on the monarch’s behalf within a specific country or territory.
-
C.
royal governor
A royal governor is a monarch-appointed official who administers and oversees a colony or territory on behalf of the crown, exercising executive authority and implementing royal policies.
-
D.
late Roman provincial governor
A late Roman provincial governor was an imperial official responsible for administering a province’s civil government, justice, taxation, and local defense under the increasingly centralized and bureaucratic structures of the later Roman Empire.
-
E.
praefectus Augustalis
The praefectus Augustalis was the Roman imperial governor of Egypt, a high-ranking equestrian official directly appointed by the emperor to administer the province’s civil, judicial, and financial affairs.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.