Triple
T4136257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Making Strides Against Breast Cancer |
E85161
|
entity |
| Predicate | fundsRaisedFor |
P33009
|
FINISHED |
| Object | American Cancer Society breast cancer 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 Cancer Society breast cancer programs | Statement: [Making Strides Against Breast Cancer, fundsRaisedFor, American Cancer Society breast cancer programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundsRaisedFor Context triple: [Making Strides Against Breast Cancer, fundsRaisedFor, American Cancer Society breast cancer programs]
-
A.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
B.
funderOf
chosen
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
C.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
D.
owedMoneyTo
Indicates that one entity has a financial obligation or debt that must be paid to another entity.
-
E.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.