Triple
T531563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdari system |
E12233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative system |
C3212
|
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: administrative system Context triple: [mansabdari system, instanceOf, administrative system]
-
A.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
system of government agencies
chosen
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
D.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
E.
public administration school
A public administration school is an educational institution that prepares students for careers in government and public service by teaching policy analysis, management, and leadership in the public sector.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.