Triple
T29443812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | saltPurpose |
P79
|
FINISHED |
| Object | defend against precomputed hash attacks |
—
|
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: defend against precomputed hash attacks | Statement: [NSEC3PARAM, saltPurpose, defend against precomputed hash attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saltPurpose Context triple: [NSEC3PARAM, saltPurpose, defend against precomputed hash attacks]
-
A.
encodingPurpose
Indicates the reason or intended use for which an encoding is created or applied.
-
B.
saltSource
Indicates that one entity serves as the origin or provider of salt for another entity or process.
-
C.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
D.
notationPurpose
Indicates that one notation is used with the specific purpose or function of representing, explaining, or supporting another entity or concept.
-
E.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1f46cc8190aeed9e77976f5cd1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:25 p.m.