Triple
T4051654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Ad Exchange |
E84598
|
entity |
| Predicate | providesToAdvertiser |
P51827
|
FINISHED |
| Object | real-time inventory access |
—
|
LITERAL 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: real-time inventory access | Statement: [Google Ad Exchange, providesToAdvertiser, real-time inventory access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesToAdvertiser Context triple: [Google Ad Exchange, providesToAdvertiser, real-time inventory access]
-
A.
providerOf
chosen
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
B.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
C.
advertisedUsing
Indicates that something is promoted or made known through a particular medium, method, or channel of advertising.
-
D.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
E.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
- F. None of above.
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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb8539148190990468c1429be9dd |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.