Triple
T29705281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDB Worldwide |
E751609
|
entity |
| Predicate | clientIndustryCoverage |
P97586
|
FINISHED |
| Object | automotive |
—
|
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: automotive | Statement: [DDB Worldwide, clientIndustryCoverage, automotive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientIndustryCoverage Context triple: [DDB Worldwide, clientIndustryCoverage, automotive]
-
A.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
-
B.
sectoralCoverage
chosen
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
-
C.
hasCustomerIndustry
Indicates that a customer is associated with or operates within a particular industry or sector.
-
D.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
E.
stakeholderIndustry
Indicates the industry or sector in which a stakeholder operates or is primarily involved.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b77cf4819099ab884963562c79 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:27 p.m.