Triple
T14971066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guam Tracking Station |
E373319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite tracking station |
C19969
|
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 tracking station Context triple: [Guam Tracking Station, instanceOf, satellite tracking station]
-
A.
deep space communications facility
chosen
A deep space communications facility is a ground-based complex equipped with large antennas, high-power transmitters, and sensitive receivers used to send commands to and receive data from spacecraft operating far beyond Earth's orbit.
-
B.
satellite system
A satellite system is an integrated network of orbiting spacecraft, ground stations, and communication links designed to perform functions such as communication, navigation, Earth observation, or scientific research.
-
C.
satellite surveillance base
A satellite surveillance base is a secure ground facility equipped with advanced antennas, control systems, and data-processing infrastructure used to monitor, receive, analyze, and manage information from surveillance satellites orbiting the Earth.
-
D.
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.
-
E.
surface station
A surface station is a ground-based facility equipped with instruments and systems to monitor, control, or communicate with external environments or assets such as weather, spacecraft, or remote sensors.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:49 a.m.