Triple
T15264067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The DAO hack |
E364853
|
entity |
| Predicate | approximateValueStolenInEther |
P117857
|
FINISHED |
| Object | about 3.6 million ETH |
—
|
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: about 3.6 million ETH | Statement: [The DAO hack, approximateValueStolenInEther, about 3.6 million ETH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateValueStolenInEther Context triple: [The DAO hack, approximateValueStolenInEther, about 3.6 million ETH]
-
A.
approximateNumberAwarded
Indicates the estimated quantity of awards or recognitions given in a particular context or event.
-
B.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
C.
valueInCents
Indicates that one entity specifies the monetary value of another entity expressed in cents.
-
D.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
E.
approximateFundsRaised
Indicates an estimated amount of money that has been raised, rather than an exact or final total.
- 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_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. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.