Triple
T8258132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMP over DDP |
E193120
|
entity |
| Predicate | typicalSNMPVersion |
P10653
|
FINISHED |
| Object | SNMPv1 |
—
|
LITERAL 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: SNMPv1 | Statement: [SNMP over DDP, typicalSNMPVersion, SNMPv1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSNMPVersion Context triple: [SNMP over DDP, typicalSNMPVersion, SNMPv1]
-
A.
protocolVersion
chosen
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
B.
exportVersionOf
Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fce9308190ac36512e80b06b52 |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.