Triple
T8814312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original PlayStation VR (via adapter) |
E209739
|
entity |
| Predicate | cableConnection |
P37306
|
FINISHED |
| Object | HDMI to console via Processor Unit |
—
|
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 to console via Processor Unit | Statement: [original PlayStation VR (via adapter), cableConnection, HDMI to console via Processor Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableConnection Context triple: [original PlayStation VR (via adapter), cableConnection, HDMI to console via Processor Unit]
-
A.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
requiresContinuousCableRun
Indicates that the relationship or action can only be fulfilled if there is an unbroken, end-to-end cable connection between the involved entities.
-
E.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another 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_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.