Triple
T17306897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gedaliah ben Ahikam |
E420186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Judean governor |
C11551
|
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: Judean governor Context triple: [Gedaliah ben Ahikam, instanceOf, Judean governor]
-
A.
Judean official
A Judean official is a governmental or administrative authority from ancient Judea responsible for overseeing civic, legal, or religious affairs within the region.
-
B.
Governor of Judah
chosen
The Governor of Judah is the appointed administrative and political leader responsible for overseeing governance, justice, and public order within the province or territory of Judah.
-
C.
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.
-
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.
Umayyad governor
An Umayyad governor was a provincial administrator appointed by the Umayyad caliphs to oversee local governance, tax collection, security, and implementation of central policies within a designated region of the caliphate.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.