Triple
T8258053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMP over OSI |
E193119
|
entity |
| Predicate | usesProtocolStack |
P1215
|
FINISHED |
| Object | OSI protocol stack |
—
|
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: OSI protocol stack | Statement: [SNMP over OSI, usesProtocolStack, OSI protocol stack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProtocolStack Context triple: [SNMP over OSI, usesProtocolStack, OSI protocol stack]
-
A.
usesProtocolSuite
chosen
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
B.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
C.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
D.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
E.
roleInProtocolStack
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
- 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.