Triple
T73446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1CM |
E1470
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
IEEE 802.1Q Time-Sensitive Networking amendments
IEEE 802.1Q Time-Sensitive Networking amendments are a set of enhancements to Ethernet bridging standards that enable deterministic, low-latency, and reliable communication for time-critical applications over standard networks.
|
E19520
|
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: IEEE 802.1Q Time-Sensitive Networking amendments | Statement: [IEEE 802.1CM, relatedTo, IEEE 802.1Q Time-Sensitive Networking amendments]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEEE 802.1Q Time-Sensitive Networking amendments Context triple: [IEEE 802.1CM, relatedTo, IEEE 802.1Q Time-Sensitive Networking amendments]
-
A.
IEEE 802.1Qbv time‑sensitive networking standard
The IEEE 802.1Qbv time‑sensitive networking standard defines enhancements to Ethernet scheduling that enable deterministic, low-latency communication for time-critical applications such as industrial automation and automotive networks.
-
B.
IEEE 802.1Qav forwarding and queuing for time‑sensitive streams standard
The IEEE 802.1Qav forwarding and queuing for time‑sensitive streams standard defines mechanisms for prioritized traffic shaping and scheduling in Ethernet networks to support low-latency, time-critical data delivery.
-
C.
IEEE 802.1Qdz TSN for mission‑critical networks standard
The IEEE 802.1Qdz TSN for mission‑critical networks standard is a Time-Sensitive Networking specification that enhances Ethernet to provide deterministic, low-latency, and highly reliable communication for safety- and mission-critical applications.
-
D.
IEEE 802.1Qdt TSN for converged networks standard
The IEEE 802.1Qdt TSN for converged networks standard is a Time-Sensitive Networking specification that enhances Ethernet to support deterministic, low-latency communication for mixed critical and non-critical traffic on converged networks.
-
E.
IEEE 802.1Qdo TSN for industrial automation standard
The IEEE 802.1Qdo TSN for industrial automation standard is a Time-Sensitive Networking specification that enhances deterministic, low-latency, and reliable Ethernet communication for industrial automation systems.
- 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: IEEE 802.1Q Time-Sensitive Networking amendments Triple: [IEEE 802.1CM, relatedTo, IEEE 802.1Q Time-Sensitive Networking amendments]
Generated description
IEEE 802.1Q Time-Sensitive Networking amendments are a set of enhancements to Ethernet bridging standards that enable deterministic, low-latency, and reliable communication for time-critical applications over standard networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IEEE 802.1Q Time-Sensitive Networking amendments Target entity description: IEEE 802.1Q Time-Sensitive Networking amendments are a set of enhancements to Ethernet bridging standards that enable deterministic, low-latency, and reliable communication for time-critical applications over standard networks.
-
A.
IEEE 802.1Qbv time‑sensitive networking standard
The IEEE 802.1Qbv time‑sensitive networking standard defines enhancements to Ethernet scheduling that enable deterministic, low-latency communication for time-critical applications such as industrial automation and automotive networks.
-
B.
IEEE 802.1Qav forwarding and queuing for time‑sensitive streams standard
The IEEE 802.1Qav forwarding and queuing for time‑sensitive streams standard defines mechanisms for prioritized traffic shaping and scheduling in Ethernet networks to support low-latency, time-critical data delivery.
-
C.
IEEE 802.1Qdz TSN for mission‑critical networks standard
The IEEE 802.1Qdz TSN for mission‑critical networks standard is a Time-Sensitive Networking specification that enhances Ethernet to provide deterministic, low-latency, and highly reliable communication for safety- and mission-critical applications.
-
D.
IEEE 802.1Qdt TSN for converged networks standard
The IEEE 802.1Qdt TSN for converged networks standard is a Time-Sensitive Networking specification that enhances Ethernet to support deterministic, low-latency communication for mixed critical and non-critical traffic on converged networks.
-
E.
IEEE 802.1Qdo TSN for industrial automation standard
The IEEE 802.1Qdo TSN for industrial automation standard is a Time-Sensitive Networking specification that enhances deterministic, low-latency, and reliable Ethernet communication for industrial automation systems.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f1a352081909cfa257202178ed6 |
completed | Feb. 28, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2d0c0b92c819091c07cbbb7dda90a |
completed | Feb. 28, 2026, 11:25 a.m. |
| NEDg | Description generation | batch_69a2d180ce20819087083946a8c1bd08 |
completed | Feb. 28, 2026, 11:29 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a2d25066548190ad8913bbe11d82ee |
completed | Feb. 28, 2026, 11:32 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.