Triple
T36487079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVS-01 |
E898961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigation satellite |
C48002
|
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: navigation satellite Context triple: [NVS-01, instanceOf, navigation satellite]
-
A.
Global Navigation Satellite System
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.
regional navigation satellite system
A regional navigation satellite system is a space-based infrastructure that provides positioning, navigation, and timing services over a specific geographic region rather than globally.
-
C.
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.
-
D.
satellite navigation infrastructure component
chosen
A satellite navigation infrastructure component is a physical or logical element—such as satellites, ground stations, control systems, or communication links—that collectively enables the generation, transmission, correction, and reception of positioning, navigation, and timing signals.
-
E.
satellite navigation system feature
A satellite navigation system feature is a specific capability or function within a satellite-based positioning system that enhances how location, routing, tracking, or related spatial information is calculated, presented, or used.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.