Triple
T2373074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT series |
E46133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian communications satellite series |
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 communications satellite series Context triple: [INSAT series, instanceOf, Indian communications satellite series]
-
A.
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.
-
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 operational objectives in space.
-
C.
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.
-
D.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
E.
expendable launch vehicle family
An expendable launch vehicle family is a series of related, single-use rockets designed to carry payloads into space and then be discarded after each mission.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:56 p.m.