Triple
T3524542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ether |
E74505
|
entity |
| Predicate | paysFor |
P18928
|
FINISHED |
| Object | state changes on Ethereum |
—
|
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: state changes on Ethereum | Statement: [Ether, paysFor, state changes on Ethereum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paysFor Context triple: [Ether, paysFor, state changes on Ethereum]
-
A.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
pays
chosen
Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
-
C.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
D.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
-
E.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.