Triple
T36484911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDA Geospatial Services |
E898910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial services provider |
C33874
|
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: geospatial services provider Context triple: [MDA Geospatial Services, instanceOf, geospatial services provider]
-
A.
geospatial company
chosen
A geospatial company is an organization that collects, analyzes, and applies location-based data and mapping technologies to provide insights, products, and services related to the Earth's surface and spatial relationships.
-
B.
geospatial web service
A geospatial web service is an online system that provides access to, processing of, and interaction with geographic data and spatial analyses over the web using standardized protocols.
-
C.
location-based services company
A location-based services company provides digital products or platforms that use geographic data and real-time positioning to deliver context-aware information, navigation, and analytics to businesses or consumers.
-
D.
geodetic service organization
A geodetic service organization is an entity that plans, conducts, and manages geodetic measurements and analyses to provide accurate reference frames, positioning data, and related geospatial services.
-
E.
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.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.