Triple
T36629947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eskenazi Health |
E904285
|
entity |
| Predicate | hasNamingBenefactors |
P200330
|
FINISHED |
| Object | Sidney Eskenazi |
—
|
NE NERFINISHED |
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: Sidney Eskenazi | Statement: [Eskenazi Health, hasNamingBenefactors, Sidney Eskenazi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingBenefactors Context triple: [Eskenazi Health, hasNamingBenefactors, Sidney Eskenazi]
-
A.
philanthropicBeneficiary
Indicates that one entity is the recipient or target of another entity’s philanthropic giving or charitable support.
-
B.
hasPhilanthropicOrganizationNamedAfter
Indicates that an entity has a philanthropic organization that is named after it.
-
C.
hasBeneficiaryTitle
Indicates that a beneficiary holds or is assigned a specific formal title or designation in the context of a relationship or arrangement.
-
D.
notablePhilanthropicBeneficiary
Indicates that an entity is a significant recipient of philanthropic donations, support, or charitable contributions from another entity.
-
E.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
- F. None of above. chosen
Provenance (4 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
| PDg | Predicate description generation | batch_69ff80d8ff208190b9e95d077fd99f78 |
completed | May 9, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:11 p.m.