Triple
T30350490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WH-1000XM5 |
E771976
|
entity |
| Predicate | headphoneType |
P169079
|
FINISHED |
| Object | closed-back |
—
|
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: closed-back | Statement: [Sony WH-1000XM5, headphoneType, closed-back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headphoneType Context triple: [Sony WH-1000XM5, headphoneType, closed-back]
-
A.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
B.
supports3_5mmJack
Indicates that one entity is compatible with or provides a 3.5mm audio jack connection for another entity.
-
C.
headstockType
Indicates the specific style or configuration of a headstock used in relation to another object or entity.
-
D.
audioJackType
Indicates the specific kind or standard of audio jack interface used or supported in the relationship.
-
E.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
- F. None of above. chosen
Provenance (4 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820b4b8c81908f5bbae956565ec0 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:56 p.m.