Triple
T11042833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Amiga 600 |
E261060
|
entity |
| Predicate | CPUClockSpeed |
P8610
|
FINISHED |
| Object | 7.14 MHz (NTSC) |
—
|
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: 7.14 MHz (NTSC) | Statement: [Commodore Amiga 600, CPUClockSpeed, 7.14 MHz (NTSC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CPUClockSpeed Context triple: [Commodore Amiga 600, CPUClockSpeed, 7.14 MHz (NTSC)]
-
A.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
clockSpeed
chosen
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
C.
supportsIntelSpeedStep
Indicates that an entity provides compatibility with or functionality for Intel SpeedStep power management technology.
-
D.
CPUCoreConfiguration
Indicates the specific arrangement and characteristics of processor cores allocated or defined within a computing system.
-
E.
operatingFrequencyApproximate
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982d42bc81908ac10f54a7b43fb7 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.