Triple
T16370784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TacSat-4 |
E397556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental military communications satellite |
C25837
|
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: experimental military communications satellite Context triple: [TacSat-4, instanceOf, experimental military communications satellite]
-
A.
military satellite
chosen
A military satellite is an artificial satellite deployed and operated by armed forces to support defense-related functions such as reconnaissance, communications, navigation, early warning, and targeting.
-
B.
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.
-
C.
space communications program
A space communications program is an organized set of missions, technologies, and operations designed to enable reliable data and signal exchange between spacecraft, satellites, and ground systems.
-
D.
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.
-
E.
space communication project
A space communication project is an organized effort to design, develop, and operate systems that enable reliable data and signal exchange between spacecraft, satellites, and ground stations.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.