Triple
T32498250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD4 |
E830583
|
entity |
| Predicate | knownCollisionAttackComplexity |
P179846
|
FINISHED |
| Object | less than 2^20 operations |
—
|
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: less than 2^20 operations | Statement: [MD4, knownCollisionAttackComplexity, less than 2^20 operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownCollisionAttackComplexity Context triple: [MD4, knownCollisionAttackComplexity, less than 2^20 operations]
-
A.
collisionAttackComplexity
Indicates the level of effort or resources required to successfully perform a collision attack against the target (e.g., a cryptographic function or system).
-
B.
attackComplexity
Indicates the level of difficulty or effort required by an attacker to successfully exploit a vulnerability or carry out an attack.
-
C.
collisionAttackKnown
Indicates that a collision-based attack method or vulnerability is known or has been discovered.
-
D.
knownAttacks
Indicates that one entity is aware of, or has information about, specific attacks associated with another entity.
-
E.
collisionResistanceTarget
Indicates that the entity serves as the designated object or system that a collision-resistance mechanism is intended to protect against successful collisions.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 12:59 a.m.