Triple
T28508652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix crypt(3) |
E721424
|
entity |
| Predicate | originalAlgorithm |
P25130
|
FINISHED |
| Object | DES-based password hash |
—
|
LITERAL 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: DES-based password hash | Statement: [Unix crypt(3), originalAlgorithm, DES-based password hash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalAlgorithm Context triple: [Unix crypt(3), originalAlgorithm, DES-based password hash]
-
A.
previousAlgorithm
Indicates that one algorithm temporally precedes another in a sequence or version history.
-
B.
originalFunction
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
C.
relatedAlgorithm
chosen
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
D.
originalSample
Indicates that one entity serves as the initial or source sample from which another related sample or derivative is obtained or based.
-
E.
introducesAlgorithm
Indicates that an entity presents or brings a specific algorithm into use, awareness, or discussion.
- F. None of above.
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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 28, 2026, 3:11 a.m.