Triple
T15171362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Mobile Ads SDK components |
E362492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile advertising SDK components |
C4105
|
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: mobile advertising SDK components Context triple: [Google Mobile Ads SDK components, instanceOf, mobile advertising SDK components]
-
A.
ad-serving technology
chosen
Ad-serving technology is a system that automatically selects, delivers, and tracks digital advertisements to users across devices and channels based on targeting rules, user data, and campaign objectives.
-
B.
online advertising platform
An online advertising platform is a digital system that enables businesses to create, manage, target, and optimize ads across websites, apps, and other online channels to reach specific audiences and achieve marketing goals.
-
C.
Android platform component
An Android platform component is a fundamental building block of an Android application (such as an Activity, Service, BroadcastReceiver, or ContentProvider) that interacts with the system and other apps to provide specific functionality within the Android operating environment.
-
D.
mobile device tracking service
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.
-
E.
advertising icon
An advertising icon is a memorable character, symbol, or figure used consistently in marketing campaigns to personify a brand and enhance its recognition and appeal.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:08 a.m.