Triple
T3419924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stitch Fix |
E72090
|
entity |
| Predicate | customerInteractionChannel |
P44485
|
FINISHED |
| Object | website |
—
|
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: website | Statement: [Stitch Fix, customerInteractionChannel, website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerInteractionChannel Context triple: [Stitch Fix, customerInteractionChannel, website]
-
A.
hasCustomerServiceChannel
chosen
Indicates that an entity provides or is associated with a specific channel or medium through which customer service interactions can occur.
-
B.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
salesChannels
Indicates the channels or methods through which a product or service is marketed, sold, or distributed to customers.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94d6808819080997df30119e71e |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.