Triple
T10532292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-256 |
E248473
|
entity |
| Predicate | collisionAttackComplexity |
P94408
|
FINISHED |
| Object | approximately 2^128 operations (idealized) |
—
|
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: approximately 2^128 operations (idealized) | Statement: [SHA-256, collisionAttackComplexity, approximately 2^128 operations (idealized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionAttackComplexity Context triple: [SHA-256, collisionAttackComplexity, approximately 2^128 operations (idealized)]
-
A.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
B.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
C.
collisionZone
Indicates a spatial region within which objects are considered to be in contact or impact with one another, typically used to detect or handle collisions.
-
D.
collisionEventAgeApproximate
Indicates an estimated or approximate age associated with a collision event.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:30 p.m.