Triple
T30025709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS VR Processor Unit |
E762874
|
entity |
| Predicate | videoPassthrough |
P83205
|
FINISHED |
| Object | HDMI |
—
|
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 | Statement: [PS VR Processor Unit, videoPassthrough, HDMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoPassthrough Context triple: [PS VR Processor Unit, videoPassthrough, HDMI]
-
A.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
B.
videoOutputConnector
chosen
Indicates a relationship where a device or component provides a connector used to output video signals to an external display or receiver.
-
C.
videoChip
Indicates a relationship where an entity functions as or contains a video-processing chip or component used for handling video signals or graphics.
-
D.
videoAdapterOptions
Indicates the configuration settings or selectable parameters associated with a video adapter or graphics device.
-
E.
videoReplayUsed
Indicates that a video replay was utilized to review or analyze a prior event or action.
- 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_69f679aaeca88190b40cb982805443ad |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:48 p.m.