Triple
T21762107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Precise Positioning Service |
E537188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-accuracy positioning service |
C20326
|
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: high-accuracy positioning service Context triple: [Precise Positioning Service, instanceOf, high-accuracy positioning service]
-
A.
high-precision positioning technique
chosen
A high-precision positioning technique is a method or system that determines the exact location of an object or point with very fine spatial accuracy, often at the centimeter or millimeter level.
-
B.
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.
-
C.
location services solution
A location services solution is a system that collects, processes, and provides geographic position data to enable location-aware features and decision-making for applications and users.
-
D.
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.
-
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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.