Triple
T13813417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Native Tribal Health Consortium |
E331951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tribal health organization |
C4075
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: tribal health organization Context triple: [Alaska Native Tribal Health Consortium, instanceOf, tribal health organization]
-
A.
tribal government agency
chosen
A tribal government agency is an administrative body established by a Native American or Indigenous tribe to manage governmental functions, deliver services, and implement policies on behalf of the tribal community.
-
B.
tribal nation
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
-
C.
community health center
A community health center is a local, patient-centered facility that provides accessible, comprehensive primary and preventive healthcare services, often focusing on underserved populations regardless of their ability to pay.
-
D.
tribal people
Tribal people are communities that maintain distinct cultural, social, and often linguistic identities, typically rooted in ancestral lands and traditional ways of life that differ from dominant national societies.
-
E.
tribally owned holding company
A tribally owned holding company is a business entity owned and controlled by a Native American tribe or tribal government that manages and oversees a portfolio of subsidiary enterprises to generate revenue, support economic development, and advance tribal sovereignty and community goals.
- F. None of above.
Provenance (1 batch)
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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.