Triple
T29443811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | iterationsPurpose |
P167430
|
FINISHED |
| Object | increase cost of dictionary 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: increase cost of dictionary attacks | Statement: [NSEC3PARAM, iterationsPurpose, increase cost of dictionary attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iterationsPurpose Context triple: [NSEC3PARAM, iterationsPurpose, increase cost of dictionary attacks]
-
A.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
B.
iterationMatrix
Indicates a matrix that represents the transformation or update applied repeatedly in an iterative process or algorithm.
-
C.
repetitionCount
Indicates the number of times a particular event, action, or pattern is repeated within a given context.
-
D.
loopLength
Indicates the length or duration of a complete cycle or loop in a repeated process, path, or sequence.
-
E.
loopsTo
Indicates that an entity has a path or connection that starts and ends at the same point, forming a loop back to itself.
- 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_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_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 3:25 p.m.