Triple
T6903179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quaestor sacri palatii |
E159542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman administrative office |
C4989
|
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: late Roman administrative office Context triple: [quaestor sacri palatii, instanceOf, late Roman administrative office]
-
A.
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.
-
B.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
C.
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.
-
D.
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.
-
E.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:25 p.m.