Triple
T36525513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koori community health services |
E900290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous health service |
C47270
|
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: Indigenous health service Context triple: [Koori community health services, instanceOf, Indigenous health service]
-
A.
First Nations health facility
A First Nations health facility is a community-centered healthcare organization that provides culturally safe, holistic medical and wellness services to First Nations individuals and families.
-
B.
Indigenous healing organization
An Indigenous healing organization is a community-based entity that provides culturally grounded, land- and tradition-informed wellness, recovery, and support services led by Indigenous knowledge keepers and practices.
-
C.
Healthcare service
chosen
A healthcare service is an organized set of medical and supportive activities provided by professionals and institutions to promote, maintain, or restore individuals’ health and well-being.
-
D.
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.
-
E.
Aboriginal community organisation
An Aboriginal community organisation is a locally governed, Aboriginal-controlled entity that delivers culturally grounded services, advocacy, and programs to support the social, economic, and cultural wellbeing of Aboriginal people and communities.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.