Triple
T15003322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | imperial administration of the Western Roman Empire |
E374145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state apparatus |
C8069
|
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: state apparatus Context triple: [imperial administration of the Western Roman Empire, instanceOf, state apparatus]
-
A.
state administration
chosen
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
B.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
C.
constitutional institution
A constitutional institution is a formally established body or office whose powers, functions, and structure are defined and limited by a constitution to uphold and operate the fundamental framework of a state.
-
D.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
E.
government of a sovereign state
The government of a sovereign state is the organized system of institutions and officials that exercises authority, makes and enforces laws, and conducts public policy on behalf of the state within its territory and in relations with other states.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.