Triple
T15264099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The DAO hack |
E364853
|
entity |
| Predicate | timeToDrainFunds |
P102409
|
FINISHED |
| Object | spread over several hours |
—
|
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: spread over several hours | Statement: [The DAO hack, timeToDrainFunds, spread over several hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToDrainFunds Context triple: [The DAO hack, timeToDrainFunds, spread over several hours]
-
A.
withdrawalEnd
Indicates the point in time or condition at which a withdrawal process or right comes to an end.
-
B.
withdrawalGracePeriod
Indicates the time window after an action or event during which a withdrawal can be made without incurring penalties or additional restrictions.
-
C.
drainFrequency
chosen
Indicates how often a draining action or process occurs between the related entities.
-
D.
drainedDuring
Indicates that one entity had its resources, energy, or contents depleted in the course of another event or process.
-
E.
drainedSince
Indicates that one entity has had its contents or resources removed starting from a specific point in time.
- 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.