Triple
T524660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keep a Child Alive |
E10891
|
entity |
| Predicate | charitableSector |
P9241
|
FINISHED |
| Object | health |
—
|
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: health | Statement: [Keep a Child Alive, charitableSector, health]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charitableSector Context triple: [Keep a Child Alive, charitableSector, health]
-
A.
fieldOfPhilanthropy
chosen
Indicates that an entity is engaged in or associated with a particular area or domain of philanthropic activity.
-
B.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
C.
nonprofitType
Indicates the specific category or classification of a nonprofit organization based on its legal or functional type.
-
D.
hasCharitableFoundation
Indicates that an entity maintains or is associated with a charitable foundation, typically for philanthropic or nonprofit activities.
-
E.
philanthropicInitiative
Indicates an action or relationship where an entity undertakes or supports activities intended to promote the welfare of others, typically through charitable or socially beneficial efforts.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b656c08190b387f21b06d99e68 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.