Triple
T32377565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium Gold 4415Y |
E827330
|
entity |
| Predicate | gpuBaseClock |
P8610
|
FINISHED |
| Object | 300 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: 300 MHz | Statement: [Intel Pentium Gold 4415Y, gpuBaseClock, 300 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gpuBaseClock Context triple: [Intel Pentium Gold 4415Y, gpuBaseClock, 300 MHz]
-
A.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
graphicsBaseFrequency
Indicates the fundamental frequency values used to control the repetition rate of a graphical pattern or effect.
-
C.
clockSpeed
chosen
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
D.
minClockSpeed
Indicates the minimum operating clock speed required or supported for a given hardware component or system.
-
E.
gpuComputePerformance
Indicates the level of processing capability a GPU can deliver for computational tasks, typically measured in operations per unit time.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c13196108190bfb822e6a3584df4 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.