Triple
T31278934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA RTX A6000 |
E797606
|
entity |
| Predicate | displayConnectors |
P171538
|
FINISHED |
| Object | 4x DisplayPort 1.4a |
—
|
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: 4x DisplayPort 1.4a | Statement: [NVIDIA RTX A6000, displayConnectors, 4x DisplayPort 1.4a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayConnectors Context triple: [NVIDIA RTX A6000, displayConnectors, 4x DisplayPort 1.4a]
-
A.
displayConnection
Indicates a relationship where one entity visually presents or shows information about its link or association to another entity.
-
B.
displayDevice
Indicates that one entity functions as a device used to visually present or output information from another entity.
-
C.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
D.
displayCapabilities
Indicates the set of functions, features, or behaviors that an entity is able to present or support in a given context.
-
E.
displayProtocol
Indicates that an entity uses or supports a particular protocol for displaying or presenting information.
- F. None of above. chosen
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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:13 p.m.