Triple
T22504114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBH |
E556344
|
entity |
| Predicate | knownForCampaign |
P4656
|
FINISHED |
| Object | Levi's advertising campaigns |
—
|
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: Levi's advertising campaigns | Statement: [BBH, knownForCampaign, Levi's advertising campaigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCampaign Context triple: [BBH, knownForCampaign, Levi's advertising campaigns]
-
A.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
notableCampaign
chosen
Indicates that an entity is prominently associated with a particular campaign, such as by leading, featuring in, or being a key focus of that campaign.
-
D.
supportedCampaignOf
Indicates that one entity actively backed, promoted, or provided assistance to the campaign associated with another entity.
-
E.
aimOfCampaign
Indicates that a campaign is directed toward achieving a particular goal or objective.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5ac5808190a66f9111c350f4dc |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.