Triple
T36514854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceansat series |
E900008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian satellite programme |
C9200
|
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: Indian satellite programme Context triple: [Oceansat series, instanceOf, Indian satellite programme]
-
A.
Indian satellite
An Indian satellite is a spaceborne artificial object designed, built, or operated by India for purposes such as communication, navigation, Earth observation, scientific research, or defense.
-
B.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or strategic objectives in space exploration and utilization.
-
C.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or operational objectives in space.
-
D.
Indian government program
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.
-
E.
satellite program
chosen
A satellite program is an organized initiative that designs, builds, launches, and operates satellites to achieve specific objectives such as communication, Earth observation, navigation, or scientific research.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.