Triple
T2357919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stream Reservation Protocol |
E47200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IEEE 802.1 protocol |
C165
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: IEEE 802.1 protocol Context triple: [Stream Reservation Protocol, instanceOf, IEEE 802.1 protocol]
-
A.
link-layer protocol
A link-layer protocol defines the rules and procedures for reliable data transfer, framing, addressing, and error handling between directly connected network devices on a physical medium.
-
B.
IEEE standard
chosen
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
C.
IETF standard
An IETF standard is a formal, consensus-based technical specification developed by the Internet Engineering Task Force that defines protocols, formats, and best practices to ensure interoperability and reliable operation of the Internet.
-
D.
packet-switched protocol
A packet-switched protocol is a communication method that breaks data into discrete packets, routes them independently across a network, and reassembles them at the destination for efficient and robust data transfer.
-
E.
network management protocol
A network management protocol is a standardized set of rules and procedures that enables monitoring, configuring, and controlling devices and services within a computer network.
- F. None of above.
Provenance (1 batch)
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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:55 p.m.