Triple
T1447549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zappos |
E31209
|
entity |
| Predicate | customerServiceChannel |
P2798
|
FINISHED |
| Object | phone support |
—
|
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: phone support | Statement: [Zappos, customerServiceChannel, phone support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerServiceChannel Context triple: [Zappos, customerServiceChannel, phone support]
-
A.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
-
D.
consultationMethod
Indicates the way or medium through which a consultation is conducted or delivered.
-
E.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55aa7dc8190aa7452d80ec8305e |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.