Triple
T32430837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-4 |
E828717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian artificial satellite |
C26885
|
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 artificial satellite Context triple: [GSAT-4, instanceOf, Indian artificial satellite]
-
A.
Indian satellite
chosen
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.
British satellite
A British satellite is an artificial object launched into orbit that is designed, built, operated, or primarily funded by the United Kingdom for purposes such as communication, navigation, Earth observation, scientific research, or military applications.
-
E.
class of artificial satellites
A class of artificial satellites comprises all human-made objects intentionally placed into orbit around celestial bodies for purposes such as communication, navigation, observation, research, and defense.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:55 a.m.