Triple
T31665895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4080 |
E808123
|
entity |
| Predicate | boostClock |
P5737
|
FINISHED |
| Object | 2505 MHz |
—
|
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: 2505 MHz | Statement: [NVIDIA GeForce RTX 4080, boostClock, 2505 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostClock Context triple: [NVIDIA GeForce RTX 4080, boostClock, 2505 MHz]
-
A.
hasClock
chosen
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
laterClockSpeed
Indicates that one entity has a higher or more advanced clock speed than another entity.
-
C.
typicalBoost
Indicates a standard or commonly expected increase in magnitude, intensity, or effectiveness associated with something.
-
D.
clockMultiplier
Indicates a relationship where one clock signal’s frequency is a specified multiple of another clock signal’s frequency.
-
E.
clockInput
Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:59 p.m.