Triple
T10329355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permissions API |
E242836
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Geolocation API |
E72259
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Geolocation API | Statement: [Permissions API, relatedTo, Geolocation API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Geolocation API Context triple: [Permissions API, relatedTo, Geolocation API]
-
A.
Geolocation API
chosen
Geolocation API is a Google Maps web service that determines a device’s approximate location using nearby cell towers, Wi-Fi nodes, and other network-based signals instead of GPS.
-
B.
Geo
Geo was a defunct General Motors automobile brand from the late 1980s and 1990s that specialized in small, economy cars often built in partnership with foreign manufacturers.
-
C.
Geo
Geo is a short form of the given name Georges, often used as an informal or familiar nickname.
-
D.
Core Location
Core Location is an Apple framework that provides location and heading services to apps, enabling them to determine a device’s geographic position and related location data.
-
E.
Geocoding API
The Geocoding API is a Google Maps web service that converts between human-readable addresses and geographic coordinates for use in mapping and location-based applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7504679ec8190926d2c5016653cea |
completed | April 9, 2026, 7:07 a.m. |
Created at: April 6, 2026, 11:52 a.m.