Triple
T14374676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DoubleClick Campaign Manager |
E356442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital advertising technology |
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: digital advertising technology Context triple: [DoubleClick Campaign Manager, instanceOf, digital advertising technology]
-
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.
digital advertising specification
A digital advertising specification is a formal document that defines the technical, creative, and delivery requirements for digital ad formats to ensure consistent implementation, compatibility, and performance across platforms and systems.
-
C.
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.
-
D.
marketing technology platform
A marketing technology platform is an integrated software system that centralizes, automates, and optimizes marketing activities across channels to improve targeting, execution, measurement, and ROI.
-
E.
online advertising company division
A specialized unit within an online advertising company responsible for planning, executing, optimizing, and analyzing digital ad campaigns for specific markets, products, or client segments.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.