Triple
T6408961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetBSD |
E127657
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | OpenSSL |
E224032
|
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: OpenSSL | Statement: [NetBSD, includes, OpenSSL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenSSL Context triple: [NetBSD, includes, OpenSSL]
-
A.
OpenSSL
chosen
OpenSSL is a widely used open-source cryptographic library and toolkit that provides SSL/TLS protocols and various encryption, hashing, and security functions for secure communication over computer networks.
-
B.
LibreSSL
LibreSSL is an open-source cryptographic library and SSL/TLS toolkit, forked from OpenSSL by the OpenBSD project to improve code quality and security.
-
C.
BoringSSL
BoringSSL is a Google-maintained fork of OpenSSL focused on security, simplicity, and suitability for large-scale, internal use in projects like Chrome and Android.
-
D.
OpenSSH
OpenSSH is a widely used open-source suite of secure networking tools that provides encrypted remote login, file transfer, and tunneling capabilities, primarily via the SSH protocol.
-
E.
PKCS #1
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638b38c888190aa2433173db64c90 |
completed | March 27, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:41 p.m.