Triple
T14593555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black culture |
E342502
|
entity |
| Predicate | hasFashionElement |
P68143
|
FINISHED |
| Object | streetwear |
—
|
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: streetwear | Statement: [Black culture, hasFashionElement, streetwear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFashionElement Context triple: [Black culture, hasFashionElement, streetwear]
-
A.
hasGarment
Indicates that one entity possesses, wears, or is associated with a particular garment.
-
B.
fashionCharacteristic
chosen
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
-
C.
clothingFeature
Indicates that one entity has a specific clothing-related attribute, detail, or characteristic associated with it.
-
D.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
-
E.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43480d8819084a707e56da2c237 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.