Triple
T20473417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEC VR4300 |
E502251
|
entity |
| Predicate | clockMultiplier |
P140225
|
FINISHED |
| Object | 1.5× of 62.5 MHz system clock in Nintendo 64 |
—
|
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.5× of 62.5 MHz system clock in Nintendo 64 | Statement: [NEC VR4300, clockMultiplier, 1.5× of 62.5 MHz system clock in Nintendo 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockMultiplier Context triple: [NEC VR4300, clockMultiplier, 1.5× of 62.5 MHz system clock in Nintendo 64]
-
A.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
B.
clockShowFrequency
Indicates how often a clock or time display is shown or updated within a given context.
-
C.
clockInput
Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of another entity.
-
D.
clockToDataRatio
Indicates the proportional relationship between a system’s clock frequency and its data transfer or processing rate.
-
E.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
- F. None of above. chosen
Provenance (4 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69962d810819091bb13fe73250e24 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:33 a.m.