Triple
T9232115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Satellite Communications Organization |
E221842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite operator |
C25836
|
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: satellite operator Context triple: [Arab Satellite Communications Organization, instanceOf, satellite operator]
-
A.
geostationary communications satellite
A geostationary communications satellite is a spacecraft positioned in an equatorial orbit that matches Earth's rotation, remaining fixed over one longitude to relay telecommunications signals between ground stations.
-
B.
television network operator
A television network operator is an organization that manages, schedules, and distributes television programming across broadcast, cable, satellite, or digital platforms to reach viewers.
-
C.
wireless operator
A wireless operator is a person or system responsible for transmitting, receiving, and managing radio-based communications over wireless networks or devices.
-
D.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
E.
satellite program
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. chosen
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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:29 p.m.