Triple
T33643627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Food Security Mission |
E861898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Government programme of India |
C44548
|
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 programme of India Context triple: [National Food Security Mission, instanceOf, Government programme of India]
-
A.
Indian government program
chosen
An Indian government program is an organized initiative launched and funded by the Government of India to address specific social, economic, or developmental objectives through targeted policies, schemes, and services.
-
B.
Indian television program
An Indian television program is a serialized or episodic audio-visual production created for broadcast or streaming in India, typically reflecting Indian cultures, languages, and entertainment preferences.
-
C.
Indian government agency
An Indian government agency is an official public-sector organization established by the Government of India to implement laws, deliver services, regulate specific domains, or execute policy and administrative functions at the national or regional level.
-
D.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
E.
federal government program
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
- 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.