Triple
T10114539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomberg American Health Initiative |
E218323
|
entity |
| Predicate | hasFundingSourceType |
P14892
|
FINISHED |
| Object | philanthropic funding |
—
|
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: philanthropic funding | Statement: [Bloomberg American Health Initiative, hasFundingSourceType, philanthropic funding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFundingSourceType Context triple: [Bloomberg American Health Initiative, hasFundingSourceType, philanthropic funding]
-
A.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
B.
funderType
chosen
Indicates the category or kind of organization or individual that provides funding in the relationship.
-
C.
secondaryFundingSource
Indicates that an entity has an additional, non-primary source of financial support or funding.
-
D.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
E.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ffcd48190825800611aab2aab |
completed | April 2, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.