Triple
T13820924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costobarus |
E332131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Herodian court official |
C12105
|
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: Herodian court official Context triple: [Costobarus, instanceOf, Herodian court official]
-
A.
Judean official
chosen
A Judean official is a governmental or administrative authority from ancient Judea responsible for overseeing civic, legal, or religious affairs within the region.
-
B.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
-
C.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
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.
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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.