Triple
T28508651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix crypt(3) |
E721424
|
entity |
| Predicate | originalSaltEncoding |
P198357
|
FINISHED |
| Object | 2-character string |
—
|
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: 2-character string | Statement: [Unix crypt(3), originalSaltEncoding, 2-character string]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSaltEncoding Context triple: [Unix crypt(3), originalSaltEncoding, 2-character string]
-
A.
saltingMethod
Indicates the technique or process used to apply salt to something, such as food or materials.
-
B.
hasSaltForm
Indicates that one chemical substance exists as, or is related to, a specific salt form of another substance.
-
C.
saltSource
Indicates that one entity serves as the origin or provider of salt for another entity or process.
-
D.
saltLengthFieldType
Indicates the data type used to represent the length of a salt value in a cryptographic or data structure context.
-
E.
primarySaltBase
Indicates that one substance serves as the main salt-forming base component in relation to another substance.
- F. None of above. chosen
Provenance (4 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_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: April 28, 2026, 3:11 a.m.