Triple
T4934593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3z |
E110781
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | IEEE 802.3ab |
E112090
|
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: IEEE 802.3ab | Statement: [IEEE 802.3z, relatedStandard, IEEE 802.3ab]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEEE 802.3ab Context triple: [IEEE 802.3z, relatedStandard, IEEE 802.3ab]
-
A.
IEEE 802.3ab
chosen
IEEE 802.3ab is an Ethernet networking standard that defines 1000BASE-T Gigabit Ethernet over Category 5 (and better) twisted-pair copper cabling.
-
B.
IEEE 802.3u
IEEE 802.3u is the Ethernet standard that defines Fast Ethernet, increasing network speeds to 100 Mbps over twisted-pair and fiber-optic cabling.
-
C.
IEEE 802.3z
IEEE 802.3z is a networking standard that defines Gigabit Ethernet over fiber-optic and short-run copper cabling.
-
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.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.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7066ed548190a76a9559f90e3869 |
completed | March 20, 2026, 4:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77b74c748190a995a26f45b79ee9 |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:30 p.m.