Triple
T12506050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Find My Mobile |
E298950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | device-locating service |
C9603
|
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: device-locating service Context triple: [Find My Mobile, instanceOf, device-locating service]
-
A.
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.
-
B.
mobile device tracking service
chosen
A mobile device tracking service is a system that continuously monitors, records, and reports the real-time or historical locations and movement patterns of mobile devices for purposes such as security, analytics, and asset management.
-
C.
location-based feature
A location-based feature is a functionality or attribute of a system that uses a user's geographic position to provide context-aware information, services, or interactions.
-
D.
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.
-
E.
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.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.