Triple
T8612069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic nRF51822 |
E203933
|
entity |
| Predicate | hasMaxClockFrequency |
P9334
|
FINISHED |
| Object | 16 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: 16 MHz | Statement: [Nordic nRF51822, hasMaxClockFrequency, 16 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxClockFrequency Context triple: [Nordic nRF51822, hasMaxClockFrequency, 16 MHz]
-
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.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
-
D.
supportsIntelSpeedStep
Indicates that an entity provides compatibility with or functionality for Intel SpeedStep power management technology.
-
E.
propertyType_maxFramerate
Indicates the maximum frame rate value that the property can support or is configured to allow.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fdf21c81908ffc6363e98ab871 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.