Triple
T53959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCP/IP |
E1063
|
entity |
| Predicate | includesProtocol |
P1393
|
FINISHED |
| Object | TLS |
E1268
|
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 | Statement: [TCP/IP, includesProtocol, TLS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS Context triple: [TCP/IP, includesProtocol, TLS]
-
A.
TLS
chosen
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
B.
Wired Equivalent Privacy
Wired Equivalent Privacy (WEP) is an early and now largely obsolete Wi‑Fi security protocol known for its weak encryption and significant vulnerabilities.
-
C.
SSH
SSH (Secure Shell) is a cryptographic network protocol used to securely access, manage, and transfer data between remote computers over unsecured networks.
-
D.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
E.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24ec4d84c81908d85a1e941dbcd19 |
completed | Feb. 28, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a255398bac81909c4ae9bba79f6c19 |
completed | Feb. 28, 2026, 2:38 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.