Triple
T32064239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Factual |
E818828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location data company |
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: location data company Context triple: [Factual, instanceOf, location data company]
-
A.
Home Location Register
A Home Location Register (HLR) is a central database in mobile networks that stores and manages subscriber information, including identities, service profiles, and current locations, to enable call routing and service delivery.
-
B.
location model
A location model is a conceptual representation that defines how spatial or geographic information is structured, stored, and related within a system or domain.
-
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.
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.
-
E.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:22 a.m.