Triple
T20638672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 200GBASE-R PHYs |
E507157
|
entity |
| Predicate | targetBitErrorRate |
P140868
|
FINISHED |
| Object | typically 10^-12 after FEC |
—
|
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: typically 10^-12 after FEC | Statement: [200GBASE-R PHYs, targetBitErrorRate, typically 10^-12 after FEC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetBitErrorRate Context triple: [200GBASE-R PHYs, targetBitErrorRate, typically 10^-12 after FEC]
-
A.
bandwidthEfficiency
Indicates how effectively available bandwidth is utilized to transmit data relative to capacity or resource usage.
-
B.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
C.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
-
D.
top5ErrorRate
Indicates the proportion of instances where the correct answer is not among the top five predicted results.
-
E.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad1163008190aa9df36750a952d2 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.