Triple
T28246334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i7-8500Y |
E712177
|
entity |
| Predicate | integratedGraphicsBaseFrequency |
P83979
|
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 Core i7-8500Y, integratedGraphicsBaseFrequency, 300 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedGraphicsBaseFrequency Context triple: [Intel Core i7-8500Y, integratedGraphicsBaseFrequency, 300 MHz]
-
A.
integratedGPUFamily
Indicates that one entity is a member of, or associated with, a particular family or series of integrated graphics processing units.
-
B.
operatingFrequencyApproximate
chosen
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
C.
supportsIntelSpeedStep
Indicates that an entity provides compatibility with or functionality for Intel SpeedStep power management technology.
-
D.
graphicsBaseFrequency
Indicates the fundamental frequency values used to control the repetition rate of a graphical pattern or effect.
-
E.
displayRefreshRate
Indicates the frequency at which a display updates its visual content, typically measured in hertz (Hz).
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 11:01 p.m.