Triple
T33643912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Mission on Agricultural Extension and Technology |
E861904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government mission |
C13367
|
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: government mission Context triple: [National Mission on Agricultural Extension and Technology, instanceOf, government mission]
-
A.
government operation
Government operation is the coordinated set of activities, processes, and procedures through which a government implements laws, delivers public services, and manages public resources to achieve policy objectives.
-
B.
government ministry
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
-
C.
government post
A government post is an official position or office within a governmental organization, held by an individual responsible for carrying out specific public duties and administrative functions.
-
D.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
E.
public service mission
chosen
A public service mission is a guiding purpose or mandate focused on delivering benefits, support, or protections to the public or a specific community, typically through government or nonprofit actions that prioritize the common good over private gain.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.