Triple
T7116541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD Duron |
E165833
|
entity |
| Predicate | maxClockSpeedApprox |
P9334
|
FINISHED |
| Object | 1.8 GHz |
—
|
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: 1.8 GHz | Statement: [AMD Duron, maxClockSpeedApprox, 1.8 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxClockSpeedApprox Context triple: [AMD Duron, maxClockSpeedApprox, 1.8 GHz]
-
A.
hasClockSpeed
chosen
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
E.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e617a528819085d4b8e1b5699966 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.