Triple
T19234770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigabit Media Independent Interface |
E480964
|
entity |
| Predicate | hasClockFrequency |
P9334
|
FINISHED |
| Object | 125 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: 125 MHz | Statement: [Gigabit Media Independent Interface, hasClockFrequency, 125 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockFrequency Context triple: [Gigabit Media Independent Interface, hasClockFrequency, 125 MHz]
-
A.
hasClockSpeed
chosen
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faeb53988190b83afee9974058c6 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.