Triple
T31036213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department for Civil Administration Personnel and for Instrumental and Financial Resources |
E790858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal branch of a ministry |
C16720
|
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: internal branch of a ministry Context triple: [Department for Civil Administration Personnel and for Instrumental and Financial Resources, instanceOf, internal branch of a ministry]
-
A.
department of a ministry
chosen
A department of a ministry is an organizational unit within a government ministry responsible for managing specific policy areas, programs, or administrative functions under the ministry’s overall mandate.
-
B.
internal administrative body
An internal administrative body is an organized group within an institution responsible for managing, coordinating, and overseeing its internal operations, policies, and support functions.
-
C.
auxiliary ministry
An auxiliary ministry is a supportive religious organization or department that assists the main church body by focusing on specific functions, services, or groups within the faith community.
-
D.
departmental institution
A departmental institution is an organized unit within a larger organization or government, responsible for managing specific functions, services, or areas of expertise under defined authority and resources.
-
E.
departmental government
A departmental government is a form of executive organization in which authority is divided among specialized departments, each headed by a minister or secretary responsible for a specific policy area.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.