Triple
T33090574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life is Why |
E846768
|
entity |
| Predicate | collectsFundsFor |
P75025
|
FINISHED |
| Object | American Heart Association programs |
—
|
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: American Heart Association programs | Statement: [Life is Why, collectsFundsFor, American Heart Association programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsFundsFor Context triple: [Life is Why, collectsFundsFor, American Heart Association programs]
-
A.
raisedMoneyFor
chosen
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
C.
donationPlatform
Indicates a relationship where an entity serves as the platform or service through which a donation is made or processed.
-
D.
fundraisingOutcome
Indicates the result or status of a fundraising effort, such as whether it met its goals or how successful it was.
-
E.
usesFundraisingMethod
Indicates that one entity employs or applies a particular fundraising method as its means of raising funds.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:26 a.m.