Triple
T3783710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savage X Fenty |
E85475
|
entity |
| Predicate | hasBrandValue |
P44541
|
FINISHED |
| Object | body inclusivity |
—
|
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: body inclusivity | Statement: [Savage X Fenty, hasBrandValue, body inclusivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandValue Context triple: [Savage X Fenty, hasBrandValue, body inclusivity]
-
A.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
B.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
D.
associatedWithBrandValues
chosen
Indicates that one entity is connected or aligned with the brand values, principles, or identity represented by another entity.
-
E.
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).
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.