Triple
T8723024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 877 |
E207057
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object |
A Standard for the Transmission of IP Datagrams on Ethernet Networks
A Standard for the Transmission of IP Datagrams on Ethernet Networks is an early Internet standards document (RFC 877) that specifies how IP packets are encapsulated and carried over Ethernet link-layer technology.
|
E752943
|
NE FINISHED |
How this triple was built (4 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: A Standard for the Transmission of IP Datagrams on Ethernet Networks | Statement: [RFC 877, title, A Standard for the Transmission of IP Datagrams on Ethernet Networks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A Standard for the Transmission of IP Datagrams on Ethernet Networks Context triple: [RFC 877, title, A Standard for the Transmission of IP Datagrams on Ethernet Networks]
-
A.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
B.
An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware is the IETF document (RFC 826) that originally specifies the Address Resolution Protocol (ARP) used to map network-layer addresses to Ethernet MAC addresses.
-
C.
IEEE 802.3 Ethernet standard
The IEEE 802.3 Ethernet standard is the foundational specification that defines wired Ethernet networking technologies, including physical media, data link layer protocols, and methods for high-speed data transmission in local and metropolitan area networks.
-
D.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
-
E.
IEEE 802 family of standards
The IEEE 802 family of standards is a collection of networking specifications that define the physical and data link layers for local and metropolitan area networks, including widely used technologies such as Ethernet and Wi‑Fi.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: A Standard for the Transmission of IP Datagrams on Ethernet Networks Triple: [RFC 877, title, A Standard for the Transmission of IP Datagrams on Ethernet Networks]
Generated description
A Standard for the Transmission of IP Datagrams on Ethernet Networks is an early Internet standards document (RFC 877) that specifies how IP packets are encapsulated and carried over Ethernet link-layer technology.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: A Standard for the Transmission of IP Datagrams on Ethernet Networks Target entity description: A Standard for the Transmission of IP Datagrams on Ethernet Networks is an early Internet standards document (RFC 877) that specifies how IP packets are encapsulated and carried over Ethernet link-layer technology.
-
A.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
B.
An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware is the IETF document (RFC 826) that originally specifies the Address Resolution Protocol (ARP) used to map network-layer addresses to Ethernet MAC addresses.
-
C.
IEEE 802.3 Ethernet standard
The IEEE 802.3 Ethernet standard is the foundational specification that defines wired Ethernet networking technologies, including physical media, data link layer protocols, and methods for high-speed data transmission in local and metropolitan area networks.
-
D.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
-
E.
IEEE 802 family of standards
The IEEE 802 family of standards is a collection of networking specifications that define the physical and data link layers for local and metropolitan area networks, including widely used technologies such as Ethernet and Wi‑Fi.
- F. None of above. chosen
Provenance (5 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0791208190b043332247372d7b |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf290001108190a90784b13a0a25b1 |
completed | April 3, 2026, 2:42 a.m. |
| NEDg | Description generation | batch_69cf2bd32cc881909ac8a61befa9929e |
completed | April 3, 2026, 2:54 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cf2c69f83481909423858668d03a8b |
completed | April 3, 2026, 2:56 a.m. |
Created at: March 30, 2026, 6:36 p.m.