Triple
T18801796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE-T1S |
E459771
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | IEEE 802.3cg |
—
|
NE NERFINISHED |
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: IEEE 802.3cg | Statement: [10BASE-T1S, partOf, IEEE 802.3cg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEEE 802.3cg Context triple: [10BASE-T1S, partOf, IEEE 802.3cg]
-
A.
IEEE 802.3cg
chosen
IEEE 802.3cg is an Ethernet standard that defines 10 Mb/s single-pair Ethernet (10BASE-T1L and 10BASE-T1S) for long-reach and short-reach industrial, automotive, and building automation applications.
-
B.
IEEE 802.3ab
IEEE 802.3ab is an Ethernet networking standard that defines 1000BASE-T Gigabit Ethernet over Category 5 (and better) twisted-pair copper cabling.
-
C.
IEEE 802.3ck
IEEE 802.3ck is an Ethernet physical layer standard that defines 100G, 200G, and 400G electrical interfaces over copper channels for high-speed data center and networking applications.
-
D.
IEEE 802.3j
IEEE 802.3j is an amendment to the IEEE 802.3 Ethernet standard that defines fiber-optic physical layer specifications for 10 Mbps Ethernet.
-
E.
IEEE 802.3br
IEEE 802.3br is an Ethernet standard that introduces frame preemption to support low-latency, time-sensitive traffic in Time-Sensitive Networking (TSN) environments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02400208190b1d84e2b0640df08 |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.