Triple
T3776834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKIMS |
E83327
|
entity |
| Predicate | designedUniformsFor |
P40514
|
FINISHED |
| Object | Team USA Olympics loungewear |
—
|
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: Team USA Olympics loungewear | Statement: [SKIMS, designedUniformsFor, Team USA Olympics loungewear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedUniformsFor Context triple: [SKIMS, designedUniformsFor, Team USA Olympics loungewear]
-
A.
modernUniformDesigner
Indicates that an entity is the designer responsible for creating or developing a modern-style uniform for another entity.
-
B.
designsFor
chosen
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
wearsOnUniform
Indicates that an item is part of and is worn as a component of a uniform.
-
D.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
-
E.
wearsUniformSimilarTo
Indicates that one entity wears a uniform that is similar in appearance or style to the uniform worn by another entity.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5be3c48190a72e840d8214bb74 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.