Triple
T63816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS |
E1268
|
entity |
| Predicate | version |
P3286
|
FINISHED |
| Object | TLS 1.3 |
E6783
|
NE 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: TLS 1.3 | Statement: [TLS, version, TLS 1.3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS 1.3 Context triple: [TLS, version, TLS 1.3]
-
A.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
B.
RFC 8446
chosen
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
C.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
D.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
E.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a25679e0688190bc0360314af3ef46 |
completed | Feb. 28, 2026, 2:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a266e8d6c48190813a2fc1578a2c12 |
completed | Feb. 28, 2026, 3:54 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.