Triple
T32862875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Owens |
E840564
|
entity |
| Predicate | signatureSilhouette |
P51216
|
FINISHED |
| Object | draped |
—
|
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: draped | Statement: [Rick Owens, signatureSilhouette, draped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureSilhouette Context triple: [Rick Owens, signatureSilhouette, draped]
-
A.
signatureFeature
chosen
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
B.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
C.
signaturePersona
Indicates that an entity serves as the primary or defining persona, identity, or character most closely associated with another entity.
-
D.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
E.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.