Triple
T8816715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPN (Next Protocol Negotiation) |
E209794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | TLS 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 extension Context triple: [NPN (Next Protocol Negotiation), instanceOf, TLS extension]
-
A.
HTTP extension
An HTTP extension is an addition to the core HTTP protocol that introduces new headers, methods, or behaviors to support extra functionality while remaining compatible with existing HTTP infrastructure.
-
B.
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.
-
C.
SMTP extension
An SMTP extension is an optional protocol enhancement that adds new commands or capabilities to the core Simple Mail Transfer Protocol to support additional email features or behaviors.
-
D.
email authentication protocol extension
An email authentication protocol extension is an add-on specification that enhances existing email authentication mechanisms (such as SPF, DKIM, or DMARC) to provide additional security, policy control, or interoperability features for verifying the legitimacy of email messages.
-
E.
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.
- F. None of above. chosen
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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:46 p.m.