Triple
T36572679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian military space programme |
E902160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military space programme |
C10566
|
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: military space programme Context triple: [Indian military space programme, instanceOf, military space programme]
-
A.
space programme of a country
The space programme of a country is the organized set of governmental and/or national initiatives, institutions, and activities dedicated to developing and operating space technologies, missions, and policies for scientific, commercial, military, and strategic purposes.
-
B.
military program
chosen
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
C.
space exploration programme
A space exploration programme is an organized, long-term initiative that plans, funds, and conducts missions and research activities to explore outer space and expand scientific and technological knowledge.
-
D.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
-
E.
space science programme
A space science programme is an organized set of research, missions, and educational activities focused on exploring and understanding space, celestial bodies, and related physical phenomena.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.