Triple
T10926793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server Name Indication extension |
E258090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protocol feature |
C993
|
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: protocol feature Context triple: [Server Name Indication extension, instanceOf, protocol feature]
-
A.
protocol service
A protocol service is a system component that implements, manages, and coordinates communication rules and message exchanges between distributed entities according to a defined protocol specification.
-
B.
protocol command
A protocol command is a structured instruction or message defined by a communication protocol that directs how participating systems should behave or exchange data.
-
C.
optional protocol
An optional protocol is a set of behaviors or methods that a class or object may implement but is not required to, allowing flexible and partial conformance to a shared interface.
-
D.
additional protocol
An additional protocol is a supplementary legal instrument that amends, clarifies, or expands the provisions of an existing treaty or agreement without replacing it.
-
E.
communication protocol
chosen
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.