Triple
T25616901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duron |
E642182
|
entity |
| Predicate | initialClockFrequencies |
P83979
|
FINISHED |
| Object | 600 MHz to 700 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: 600 MHz to 700 MHz | Statement: [Duron, initialClockFrequencies, 600 MHz to 700 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialClockFrequencies Context triple: [Duron, initialClockFrequencies, 600 MHz to 700 MHz]
-
A.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
B.
minClockSpeed
Indicates the minimum operating clock speed required or supported for a given hardware component or system.
-
C.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
D.
operatingFrequencyApproximate
chosen
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
E.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5 p.m.