Triple
T4425468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overture Services |
E95196
|
entity |
| Predicate | servedClients |
P734
|
FINISHED |
| Object | online 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: online advertisers | Statement: [Overture Services, servedClients, online advertisers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClients Context triple: [Overture Services, servedClients, online advertisers]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
hasClient
chosen
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
C.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
D.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
E.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554e40ec8190982acc0948da2f42 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.