Triple
T23655072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategos of Judea |
E584275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic-era governorship |
C40456
|
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: Hellenistic-era governorship Context triple: [Strategos of Judea, instanceOf, Hellenistic-era governorship]
-
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.
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.
-
C.
Hellenistic institution
chosen
A Hellenistic institution is an organized social, political, religious, or educational structure that developed or operated within the culturally blended Greek-influenced societies of the Hellenistic period (c. 323–31 BCE).
-
D.
ancient Greek officials
Ancient Greek officials were public functionaries appointed or elected within the city-states to administer civic, religious, military, and judicial duties according to local laws and customs.
-
E.
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.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:49 p.m.