Triple
T7032976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 80486 |
E163312
|
entity |
| Predicate | typicalClockSpeedRange |
P9334
|
FINISHED |
| Object | 20 MHz to 100 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: 20 MHz to 100 MHz | Statement: [Intel 80486, typicalClockSpeedRange, 20 MHz to 100 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClockSpeedRange Context triple: [Intel 80486, typicalClockSpeedRange, 20 MHz to 100 MHz]
-
A.
hasClockSpeed
chosen
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
C.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
D.
typicalRAMRangeMB
Indicates the usual or expected range of RAM capacity, measured in megabytes, associated with an entity.
-
E.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.