Triple
T4051583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google AdSense |
E84597
|
entity |
| Predicate | adProvider |
P51827
|
FINISHED |
| Object | Google Ads advertisers |
—
|
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: Google Ads advertisers | Statement: [Google AdSense, adProvider, Google Ads advertisers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adProvider Context triple: [Google AdSense, adProvider, Google Ads advertisers]
-
A.
landerProvider
Indicates the organization or entity responsible for providing or operating the lander used in a mission or operation.
-
B.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
C.
providerOf
chosen
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
D.
mediaAssociation
Indicates a relationship where one media item is linked, connected, or otherwise associated with another entity or media resource.
-
E.
usesAdvertisingModel
Indicates that one entity employs or relies on another entity’s advertising-based business or revenue model.
- 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.