Triple
T12673717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soap & Glory |
E302749
|
entity |
| Predicate | hasBrandPersonality |
P87955
|
FINISHED |
| Object | playful |
—
|
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: playful | Statement: [Soap & Glory, hasBrandPersonality, playful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandPersonality Context triple: [Soap & Glory, hasBrandPersonality, playful]
-
A.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
B.
hasBrandConcept
chosen
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
-
C.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
D.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
E.
associatedBrandCulture
Indicates a relationship where a brand is linked to, reflects, or is characterized by a particular culture, set of values, or shared norms.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.