Triple
T20271170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-LX4 |
E499095
|
entity |
| Predicate | perLaneDataRate |
P1376
|
FINISHED |
| Object | 2.5 Gbit/s per wavelength (approximate) |
—
|
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: 2.5 Gbit/s per wavelength (approximate) | Statement: [10GBASE-LX4, perLaneDataRate, 2.5 Gbit/s per wavelength (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perLaneDataRate Context triple: [10GBASE-LX4, perLaneDataRate, 2.5 Gbit/s per wavelength (approximate)]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
maxTheoreticalBandwidthPerSlot
Indicates the maximum possible data transfer capacity that can be achieved per individual slot under ideal conditions.
-
C.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
D.
hasMaximumBandwidth
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
E.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675de35188190840dc7d04c1d5fd9 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.