Triple
T4051676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenRTB |
E84599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time bidding specification |
C3606
|
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: real-time bidding specification Context triple: [OpenRTB, instanceOf, real-time bidding specification]
-
A.
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.
-
B.
interoperability specification suite
chosen
An interoperability specification suite is a coordinated set of technical standards, protocols, and guidelines designed to ensure that diverse systems, components, or organizations can reliably exchange and correctly interpret data and functionality.
-
C.
W3C specification
A W3C specification is an official, collaboratively developed technical standard published by the World Wide Web Consortium that defines interoperable protocols, formats, and best practices for the World Wide Web.
-
D.
W3C technical specification
A W3C technical specification is a formal, consensus-based document published by the World Wide Web Consortium that defines standards, protocols, and guidelines to ensure the interoperability and evolution of the World Wide Web.
-
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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:37 p.m.