Triple
T9468134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shriners International |
E228322
|
entity |
| Predicate | providesCareRegardlessOfAbilityToPay |
P88285
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shriners International, providesCareRegardlessOfAbilityToPay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesCareRegardlessOfAbilityToPay Context triple: [Shriners International, providesCareRegardlessOfAbilityToPay, yes]
-
A.
hasEmergencyCare
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
-
B.
healthcareAccess
Indicates the degree to which individuals can obtain and use needed health care services.
-
C.
providesCareSetting
Indicates that one entity serves as the care environment or setting in which another entity receives or delivers care.
-
D.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
-
E.
paymentAtPointOfCare
Indicates that a payment is made directly at the time and place where the care or service is provided.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdf604481909bf7d7d477230ca3 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:53 p.m.