Triple
T13848484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest 2 |
E332870
|
entity |
| Predicate | USBPortType |
P104380
|
FINISHED |
| Object | USB-C |
—
|
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: USB-C | Statement: [Oculus Quest 2, USBPortType, USB-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USBPortType Context triple: [Oculus Quest 2, USBPortType, USB-C]
-
A.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
B.
usbCPortSpecification
Indicates that one entity defines or conforms to the technical specifications of a USB-C port used by another entity.
-
C.
usbCPortsCount
Indicates the number of USB-C ports that an entity has.
-
D.
hasUSBDevicePortCount
Indicates the number of USB device ports that an entity possesses or supports.
-
E.
usbFeatures
chosen
Indicates that there exists a relationship specifying the USB-related capabilities or characteristics supported by an 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b2a9788190b164760adec64ef6 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.