Triple
T33231127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1269 |
E850694
|
entity |
| Predicate | usesProtocolAcronym |
P9964
|
FINISHED |
| Object | SNMP |
—
|
NE NERFINISHED |
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 1269, usesProtocolAcronym, SNMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProtocolAcronym Context triple: [RFC 1269, usesProtocolAcronym, SNMP]
-
A.
includeProtocol
Indicates that one entity incorporates or makes use of a specified protocol as part of its operation or definition.
-
B.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
C.
hasProtocol
chosen
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
D.
protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
-
E.
mayUseProtocol
Indicates that an entity is permitted or authorized to employ a specified protocol for communication or operation.
- F. None of above.
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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.