Triple
T11077996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian National Space Promotion and Authorisation Centre |
E261916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space agency regulator |
C11517
|
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: space agency regulator Context triple: [Indian National Space Promotion and Authorisation Centre, instanceOf, space agency regulator]
-
A.
space agency oversight body
chosen
A space agency oversight body is an authoritative organization responsible for monitoring, evaluating, and guiding a space agency’s policies, programs, safety, and compliance to ensure accountability, effectiveness, and alignment with national or international objectives.
-
B.
space agency
A space agency is an organization, typically government-funded, responsible for planning, developing, and conducting space missions, research, and related technologies.
-
C.
space-grant institution
A space-grant institution is a college or university designated under the U.S. National Space Grant College and Fellowship Program to promote education, research, and public outreach in space-related fields.
-
D.
mission agency
A mission agency is an organization that recruits, equips, sends, and supports missionaries or mission teams to carry out religious, humanitarian, or development work across different regions or cultures.
-
E.
aerospace organization
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.