Triple
T8234992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2571 |
E192382
|
entity |
| Predicate | protocolAcronym |
P36183
|
FINISHED |
| Object | SNMP |
E5625
|
NE FINISHED |
How this triple was built (2 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: SNMP | Statement: [RFC 2571, protocolAcronym, SNMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SNMP Context triple: [RFC 2571, protocolAcronym, SNMP]
-
A.
SNMP
chosen
SNMP (Simple Network Management Protocol) is a standard Internet protocol used to monitor, manage, and configure network devices such as routers, switches, and servers.
-
B.
SNMPv3
SNMPv3 is the third version of the Simple Network Management Protocol, notable for adding robust security features such as authentication and encryption for managing network devices.
-
C.
SNMPv1
SNMPv1 is the first version of the Simple Network Management Protocol, used for basic network device monitoring and management over IP networks.
-
D.
SNMPv2c
SNMPv2c is a version of the Simple Network Management Protocol that uses community-based security and is widely deployed for network device monitoring and management.
-
E.
SNMP over OSI
SNMP over OSI is a specification for running the Simple Network Management Protocol on top of the OSI protocol stack instead of the traditional TCP/IP stack.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782931848190bcc54622f34e06a7 |
completed | March 31, 2026, 7:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd34f0a770819089520e689ca9937a |
completed | April 1, 2026, 3:08 p.m. |
Created at: March 30, 2026, 5:46 p.m.