Triple
T3406058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodian |
E71774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | client ruler under 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: client ruler under Rome Context triple: [Herodian, instanceOf, client ruler under 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.
Roman censor
A Roman censor was a high-ranking magistrate responsible for conducting the census, overseeing public morals, and managing certain aspects of state finances and public works in the Roman Republic.
-
C.
1st-century ruler
A 1st-century ruler is a sovereign or political leader who held authority over a state or territory during the years 1 to 100 CE, shaping early historical, cultural, and geopolitical developments of that era.
-
D.
Western Roman emperor
A Western Roman emperor is the sovereign ruler of the western half of the Roman Empire, holding supreme political, military, and religious authority from the late 3rd to the late 5th century CE.
-
E.
Nero's advisor
Nero's advisor is a trusted counselor who provides strategic, political, and personal guidance to the Roman Emperor Nero, influencing his decisions and actions behind the scenes.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.