Triple
T4370930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100BASE-X |
E98892
|
entity |
| Predicate | clockRateOnMedium |
P54871
|
FINISHED |
| Object | 125 MBd for 4B/5B-coded variants |
—
|
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 MBd for 4B/5B-coded variants | Statement: [100BASE-X, clockRateOnMedium, 125 MBd for 4B/5B-coded variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockRateOnMedium Context triple: [100BASE-X, clockRateOnMedium, 125 MBd for 4B/5B-coded variants]
-
A.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
B.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
C.
clockToDataRatio
Indicates the proportional relationship between a system’s clock frequency and its data transfer or processing rate.
-
D.
mode2BitRate
chosen
Indicates the data transmission rate associated with a specific operational mode.
-
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.
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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521cb7ec8190b7b79675871d97d8 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.