Triple
T31632350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4090 |
E807201
|
entity |
| Predicate | supportsBroadcastFeatures |
P203
|
FINISHED |
| Object | NVIDIA Broadcast |
E750842
|
NE 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: NVIDIA Broadcast | Statement: [NVIDIA GeForce RTX 4090, supportsBroadcastFeatures, NVIDIA Broadcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBroadcastFeatures Context triple: [NVIDIA GeForce RTX 4090, supportsBroadcastFeatures, NVIDIA Broadcast]
-
A.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
D.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
-
E.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
- F. None of above.
Provenance (4 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79d68d448190b3c64dad67831108 |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:45 p.m.