Triple
T21191028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IGMPv1 |
E522210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IGMP version |
C28561
|
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: IGMP version Context triple: [IGMPv1, instanceOf, IGMP version]
-
A.
Internet Protocol version
An Internet Protocol version is a specific iteration of the Internet Protocol standard that defines how data packets are formatted, addressed, transmitted, and routed across interconnected networks.
-
B.
multicast registration protocol
chosen
A multicast registration protocol is a network mechanism that allows hosts or routers to dynamically join, leave, and advertise membership in multicast groups so that multicast traffic is efficiently delivered only to interested receivers.
-
C.
G.hn standard
The G.hn standard is a unified home networking specification that enables high-speed data transmission over existing wiring infrastructures such as power lines, phone lines, and coaxial cables within a building.
-
D.
IEEE 802.21 feature set
The IEEE 802.21 feature set comprises mechanisms and protocols that enable seamless media-independent handover and service continuity across heterogeneous wireless and wired networks.
-
E.
Management Information Base specification
A Management Information Base specification defines the structured set of managed objects, their attributes, and relationships used by network management protocols (such as SNMP) to monitor and control devices in a networked environment.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.