Triple
T1798454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.0 |
E39658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Transport Layer Security version |
C995
|
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: Transport Layer Security version Context triple: [TLS 1.0, instanceOf, Transport Layer Security version]
-
A.
Internet Protocol version
An Internet Protocol version is a specific iteration of the Internet Protocol standard that defines how data packets are formatted, addressed, transmitted, and routed across interconnected networks.
-
B.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
C.
network security protocol
chosen
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
D.
Thunderbolt version
A Thunderbolt version represents a specific generation of the Thunderbolt hardware interface standard, defining its data transfer speeds, power delivery capabilities, connector type, and supported protocols.
-
E.
internet protocol suite
The internet protocol suite is a conceptual framework of layered communication protocols (including TCP/IP) that defines how data is formatted, addressed, transmitted, routed, and received across interconnected computer networks.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.