Triple
T30025710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS VR Processor Unit |
E762874
|
entity |
| Predicate | audioInterface |
P33360
|
FINISHED |
| Object | HDMI audio |
—
|
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: HDMI audio | Statement: [PS VR Processor Unit, audioInterface, HDMI audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioInterface Context triple: [PS VR Processor Unit, audioInterface, HDMI audio]
-
A.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
B.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
C.
audioBackend
Indicates the audio processing or playback system used to handle sound for a given entity or context.
-
D.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
-
E.
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.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:48 p.m.