Triple
T15264080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The DAO hack |
E364853
|
entity |
| Predicate | exploitTechnique |
P5659
|
FINISHED |
| Object | repeated recursive withdrawals |
—
|
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: repeated recursive withdrawals | Statement: [The DAO hack, exploitTechnique, repeated recursive withdrawals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitTechnique Context triple: [The DAO hack, exploitTechnique, repeated recursive withdrawals]
-
A.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
B.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
-
C.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
D.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
-
E.
attackToolExample
chosen
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.