Triple
T16854018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDirect |
E409741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | programmatic advertising specification |
C14892
|
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: programmatic advertising specification Context triple: [OpenDirect, instanceOf, programmatic advertising specification]
-
A.
digital advertising specification
chosen
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.
-
B.
ad-serving technology
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.
-
C.
XML-based ad playlist format
An XML-based ad playlist format is a structured markup specification that defines the sequence, timing, metadata, and delivery parameters of advertisements for automated playback across digital media platforms.
-
D.
IAB standard
IAB standard is a set of industry-defined guidelines and technical specifications created by the Interactive Advertising Bureau to ensure consistency, interoperability, and best practices in digital advertising.
-
E.
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.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.