Triple
T27692239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS heartbeat extension |
E698189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | TLS protocol extension |
C25115
|
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: TLS protocol extension Context triple: [TLS heartbeat extension, instanceOf, TLS protocol extension]
-
A.
TLS extension
chosen
A TLS extension is an optional, standardized addition to the TLS protocol that allows clients and servers to negotiate extra capabilities or parameters (such as supported protocols, server names, or security features) during the handshake.
-
B.
SSH extension specification
An SSH extension specification defines the standardized structure, semantics, and negotiation rules for optional SSH protocol features that extend core SSH functionality while maintaining interoperability and security.
-
C.
IETF protocol extension
An IETF protocol extension is a standardized enhancement or modification to an existing Internet protocol, defined through the IETF process to add new capabilities, improve performance, or address emerging requirements while maintaining interoperability.
-
D.
IRC protocol extension
An IRC protocol extension is an enhancement or add-on to the core Internet Relay Chat protocol that introduces additional commands, features, or behaviors while remaining compatible with existing IRC infrastructure.
-
E.
IPsec extension
An IPsec extension is a conceptual class that augments core IPsec functionality with additional security, configuration, or protocol features to support enhanced or specialized network protection requirements.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:52 p.m.