Triple
T29020442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tartar Control Duff |
E737437
|
entity |
| Predicate | marketingStyle |
P116094
|
FINISHED |
| Object | parody advertising |
—
|
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: parody advertising | Statement: [Tartar Control Duff, marketingStyle, parody advertising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingStyle Context triple: [Tartar Control Duff, marketingStyle, parody advertising]
-
A.
marketingTone
chosen
Indicates that one entity communicates with another using language or style intended to promote, persuade, or influence perception, typically for marketing or advertising purposes.
-
B.
brandingStyle
Indicates the specific visual and stylistic approach used to represent a brand’s identity.
-
C.
marketingEmphasized
Indicates that a marketing effort or message is given special focus, prominence, or priority relative to other aspects or activities.
-
D.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
E.
productStyle
Indicates the stylistic category or design theme that characterizes a product.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 9:48 a.m.