Triple
T33027980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCRAM-SHA-1 |
E845091
|
entity |
| Predicate | passwordStorageModel |
P91403
|
FINISHED |
| Object | salted password verifier |
—
|
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: salted password verifier | Statement: [SCRAM-SHA-1, passwordStorageModel, salted password verifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passwordStorageModel Context triple: [SCRAM-SHA-1, passwordStorageModel, salted password verifier]
-
A.
passwordStorageRequirement
Indicates that there is a specified condition or standard governing how passwords must be stored.
-
B.
storesPasswordAs
chosen
Indicates that one entity keeps or maintains another entity’s password in a particular form or location.
-
C.
passwordProtectedBy
Indicates that access to an entity is restricted and can only be obtained by providing a specific password associated with another entity.
-
D.
usedPassword
Indicates that one entity has employed or entered another entity as a password for authentication or access.
-
E.
passwordSpace
Indicates the set of all possible passwords that can be formed under a given password policy or constraints.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.