Triple
T5667204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3ck |
E124884
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | 200GBASE-CR2 |
E542559
|
NE 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: 200GBASE-CR2 | Statement: [IEEE 802.3ck, defines, 200GBASE-CR2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 200GBASE-CR2 Context triple: [IEEE 802.3ck, defines, 200GBASE-CR2]
-
A.
200GBASE-KR2
chosen
200GBASE-KR2 is an Ethernet physical layer standard for 200 Gbit/s transmission over backplane copper links using two electrical lanes.
-
B.
100GBASE-KR1
100GBASE-KR1 is an Ethernet physical layer standard for 100 Gb/s data transmission over a single lane of backplane copper.
-
C.
10GBASE-E
10GBASE-E is a 10 Gigabit Ethernet physical layer standard that uses long-wavelength optics to support long-distance data transmission over single-mode fiber.
-
D.
10GBASE-SR
10GBASE-SR is a 10 Gigabit Ethernet standard for short-range data transmission over multimode fiber, commonly used in data centers and enterprise networks.
-
E.
200 Gigabit Ethernet
200 Gigabit Ethernet is a high-speed Ethernet standard that provides 200 Gbit/s data transmission for data centers and high-performance networking applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02345004081908858867be48d3885 |
completed | March 22, 2026, 5:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07dc047b08190a3afde7e9984062d |
completed | March 22, 2026, 11:39 p.m. |
Created at: March 22, 2026, 3:43 p.m.