Triple
T29216105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Follow |
E740670
|
entity |
| Predicate | hasMarketingPurpose |
P199210
|
FINISHED |
| Object | brand promotion for BMW |
—
|
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: brand promotion for BMW | Statement: [The Follow, hasMarketingPurpose, brand promotion for BMW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketingPurpose Context triple: [The Follow, hasMarketingPurpose, brand promotion for BMW]
-
A.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
B.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
C.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
D.
hasMarketingPoint
Indicates that an entity possesses or is associated with a specific marketing-related feature, advantage, or talking point.
-
E.
hasMarketingClaim
Indicates that an entity asserts or is associated with a specific marketing claim about a product, service, or brand.
- F. None of above. chosen
Provenance (4 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
| PDg | Predicate description generation | batch_69ff263632608190a99beb73608066d8 |
completed | May 9, 2026, 12:19 p.m. |
Created at: April 28, 2026, 12:13 p.m.