Triple
T8814306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original PlayStation VR (via adapter) |
E209739
|
entity |
| Predicate | headphones |
P33360
|
FINISHED |
| Object | 3.5 mm headphone jack on headset cable |
—
|
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: 3.5 mm headphone jack on headset cable | Statement: [original PlayStation VR (via adapter), headphones, 3.5 mm headphone jack on headset cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headphones Context triple: [original PlayStation VR (via adapter), headphones, 3.5 mm headphone jack on headset cable]
-
A.
earDescription
Indicates a textual description of the characteristics or appearance of an entity’s ear or ears.
-
B.
hasMicrophones
Indicates that one entity possesses, includes, or is equipped with one or more microphones.
-
C.
audioPorts
chosen
Indicates that one entity provides or is equipped with audio input/output ports that can be used or connected by the other entity.
-
D.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
E.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.