Triple
T16920841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Regulated Service |
E410439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite navigation service |
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: satellite navigation service Context triple: [Public Regulated Service, instanceOf, satellite navigation service]
-
A.
GNSS service organization
An organization that plans, operates, maintains, and manages Global Navigation Satellite System (GNSS) infrastructure and services to provide reliable positioning, navigation, and timing information to users.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
terrestrial navigation system
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.