Triple
T9978254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTLM |
E196384
|
entity |
| Predicate | storesPasswordAs |
P91403
|
FINISHED |
| Object | hash rather than plaintext |
—
|
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: hash rather than plaintext | Statement: [NTLM, storesPasswordAs, hash rather than plaintext]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesPasswordAs Context triple: [NTLM, storesPasswordAs, hash rather than plaintext]
-
A.
passwordStorageRequirement
Indicates that there is a specified condition or standard governing how passwords must be stored.
-
B.
advantageOverPasswords
Indicates that one method, system, or approach provides benefits or improvements compared to traditional password-based authentication.
-
C.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
D.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
E.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84ef8ac8190abbe78b7611c5309 |
completed | April 2, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:49 p.m.