Triple
T31632341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4090 |
E807201
|
entity |
| Predicate | supportsHdmi |
P79781
|
FINISHED |
| Object | HDMI 2.1 |
—
|
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 2.1 | Statement: [NVIDIA GeForce RTX 4090, supportsHdmi, HDMI 2.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHdmi Context triple: [NVIDIA GeForce RTX 4090, supportsHdmi, HDMI 2.1]
-
A.
hasHDMIPort
Indicates that one entity (typically a device) is equipped with an HDMI port that can be used to connect to another entity.
-
B.
hdmiVersion
chosen
Indicates the specific HDMI standard or version associated with a device, port, or connection.
-
C.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
D.
hasMicroHDMI
Indicates that one entity is equipped with or includes a Micro HDMI (HDMI Type D) port or connector.
-
E.
supportsHDRFormat
Indicates that one entity is capable of handling, displaying, or processing content encoded in a specified High Dynamic Range (HDR) format for 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:45 p.m.