Triple
T28906368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Administrative Model for Version 2 of the Simple Network Management Protocol (SNMPv2) |
E733094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SNMPv2 administrative model specification |
C2028
|
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: SNMPv2 administrative model specification Context triple: [Administrative Model for Version 2 of the Simple Network Management Protocol (SNMPv2), instanceOf, SNMPv2 administrative model specification]
-
A.
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.
-
B.
ASN.1 standard
The ASN.1 standard is a formal notation used to define, encode, transmit, and decode structured data in a platform- and language-independent way, commonly used in telecommunications and cryptographic protocols.
-
C.
YANG data model standard
A YANG data model standard is a formal, structured language used to model configuration and state data for network devices and services in a vendor-neutral, interoperable way.
-
D.
network management protocol
chosen
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.
-
E.
Object Management Group specification
An Object Management Group specification is a standardized, vendor-neutral technical document that defines interoperable models, interfaces, and protocols for distributed, model-driven, and middleware-based systems.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 8:07 a.m.