Triple
T3192592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gila River Indian Community |
E66857
|
entity |
| Predicate | hasHealthService |
P6787
|
FINISHED |
| Object | tribal health care system |
—
|
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: tribal health care system | Statement: [Gila River Indian Community, hasHealthService, tribal health care system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthService Context triple: [Gila River Indian Community, hasHealthService, tribal health care system]
-
A.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
B.
hasHealthServicesCoordination
Indicates that one entity is responsible for organizing, managing, or facilitating access to health-related services for another entity.
-
C.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
D.
hasServiceTo
chosen
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e8e4b48190bc7c6443fc6da900 |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.