Triple
T6598444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doublemint |
E148534
|
entity |
| Predicate | usedInMarketingSlogan |
P23420
|
FINISHED |
| Object | Double your pleasure, double your fun |
—
|
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: Double your pleasure, double your fun | Statement: [Doublemint, usedInMarketingSlogan, Double your pleasure, double your fun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMarketingSlogan Context triple: [Doublemint, usedInMarketingSlogan, Double your pleasure, double your fun]
-
A.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
B.
associatedWithFamousSlogan
chosen
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
C.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
-
D.
sloganInEnglish
Indicates that an entity’s slogan is expressed in the English language.
-
E.
sloganCategory
Indicates that a slogan is classified as belonging to a particular category or type.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.