Triple

T12987

Position	Surface form	Disambiguated ID	Type / Status
Subject	IEEE Standards Association	`E260`	entity
Predicate	develops	`P73`	FINISHED
Object	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.	`E16998`	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.1Qdz TSN for mission‑critical networks standard | Statement: [IEEE Standards Association, develops, IEEE 802.1Qdz TSN for mission‑critical networks standard]

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: IEEE 802.1Qdz TSN for mission‑critical networks standard
Context triple: [IEEE Standards Association, develops, IEEE 802.1Qdz TSN for mission‑critical networks standard]

A. 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.
B. IEEE 802.1Qdx TSN for data centers standard
The IEEE 802.1Qdx TSN for data centers standard is a Time-Sensitive Networking specification that defines mechanisms to provide deterministic, low-latency, and reliable Ethernet communication tailored for modern data center environments.
C. IEEE 802.1Qds TSN for public networks standard
The IEEE 802.1Qds TSN for public networks standard is a Time-Sensitive Networking specification that extends Ethernet capabilities to support deterministic, low-latency communication across large-scale public networks.
D. 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.
E. IEEE 802.1Qdy TSN for industrial IoT standard
IEEE 802.1Qdy TSN for industrial IoT is a Time-Sensitive Networking extension that enhances deterministic, low-latency, and reliable Ethernet communication tailored for industrial Internet of Things applications.
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.1Qdz TSN for mission‑critical networks standard
Triple: [IEEE Standards Association, develops, IEEE 802.1Qdz TSN for mission‑critical networks standard]

Generated description

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.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: IEEE 802.1Qdz TSN for mission‑critical networks standard
Target entity description: 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.

A. 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.
B. IEEE 802.1Qdx TSN for data centers standard
The IEEE 802.1Qdx TSN for data centers standard is a Time-Sensitive Networking specification that defines mechanisms to provide deterministic, low-latency, and reliable Ethernet communication tailored for modern data center environments.
C. IEEE 802.1Qds TSN for public networks standard
The IEEE 802.1Qds TSN for public networks standard is a Time-Sensitive Networking specification that extends Ethernet capabilities to support deterministic, low-latency communication across large-scale public networks.
D. 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.
E. IEEE 802.1Qdy TSN for industrial IoT standard
IEEE 802.1Qdy TSN for industrial IoT is a Time-Sensitive Networking extension that enhances deterministic, low-latency, and reliable Ethernet communication tailored for industrial Internet of Things applications.
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_69a23d7ad88c8190bffe8ab091d86642`	completed	Feb. 28, 2026, 12:57 a.m.
NER	Named-entity recognition	`batch_69a240014418819090625e2fb774a2e6`	completed	Feb. 28, 2026, 1:08 a.m.
NED1	Entity disambiguation (via context triple)	`batch_69a2bf62f0f481909e1efb2f3b903694`	completed	Feb. 28, 2026, 10:11 a.m.
NEDg	Description generation	`batch_69a2bfc230b0819084d773474e8fcbfe`	completed	Feb. 28, 2026, 10:13 a.m.
NED2	Entity disambiguation (via description)	`batch_69a2c09721a88190a6268360c34a0b01`	completed	Feb. 28, 2026, 10:16 a.m.

Created at: Feb. 28, 2026, 1:02 a.m.