Triple
T28508632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix crypt(3) |
E721424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | password hashing function |
C3162
|
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: password hashing function Context triple: [Unix crypt(3), instanceOf, password hashing function]
-
A.
cryptographic primitive
chosen
A cryptographic primitive is a low-level, well-defined algorithm or protocol (such as a hash function, block cipher, or digital signature scheme) that serves as a basic building block for constructing more complex cryptographic systems and protocols.
-
B.
password cracking tool
A password cracking tool is a software application designed to recover or guess passwords by systematically testing possible combinations or exploiting weaknesses in password storage mechanisms.
-
C.
cryptographic library
A cryptographic library is a collection of software routines that implement cryptographic algorithms and protocols to provide secure encryption, decryption, hashing, key management, and related security functions for applications.
-
D.
crypt
A crypt is an underground chamber, typically beneath a church or cemetery, used for burials, storage of sacred relics, or as a place of remembrance for the dead.
-
E.
cryptographic key
A cryptographic key is a piece of information, usually a string of bits, used by cryptographic algorithms to encrypt, decrypt, sign, or verify data securely.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:11 a.m.