Triple
T14999602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day of Giving |
E374048
|
entity |
| Predicate | donationRecipientType |
P12761
|
FINISHED |
| Object | nonprofit organizations |
—
|
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: nonprofit organizations | Statement: [Day of Giving, donationRecipientType, nonprofit organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: donationRecipientType Context triple: [Day of Giving, donationRecipientType, nonprofit organizations]
-
A.
beneficiaryType
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
B.
philanthropicBeneficiary
Indicates that one entity is the recipient or target of another entity’s philanthropic giving or charitable support.
-
C.
typeOfDonations
Indicates the kinds or categories of donations involved in a given context or transaction.
-
D.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
E.
organizationRecipient
chosen
Indicates that an organization is the recipient or beneficiary of something provided, sent, or directed by another entity.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.