Triple
T6327381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Navigation Satellite System Infrastructure |
E141893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space-based PNT system |
C7161
|
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: space-based PNT system Context triple: [Global Navigation Satellite System Infrastructure, instanceOf, space-based PNT system]
-
A.
Global Navigation Satellite System
chosen
A Global Navigation Satellite System is a satellite-based infrastructure that provides continuous, worldwide positioning, navigation, and timing services to receivers on or near Earth’s surface.
-
B.
GNSS reference network
A GNSS reference network is a coordinated system of continuously operating GNSS stations that provide precise, stable positioning and timing references for surveying, navigation, and geospatial applications.
-
C.
space transportation system
A space transportation system is an integrated set of vehicles, infrastructure, and operations designed to move payloads and passengers between Earth and space or between locations in space.
-
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.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.