Triple
T30588815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-1000XM2 |
E778591
|
entity |
| Predicate | includedAccessory |
P16605
|
FINISHED |
| Object | audio cable for wired connection |
—
|
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: audio cable for wired connection | Statement: [Sony WI-1000XM2, includedAccessory, audio cable for wired connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedAccessory Context triple: [Sony WI-1000XM2, includedAccessory, audio cable for wired connection]
-
A.
accessory
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
B.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
E.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:24 p.m.