Triple
T31466759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōhanga Reo |
E802738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous language revitalization initiative |
C3652
|
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 language revitalization initiative Context triple: [Kōhanga Reo, instanceOf, indigenous language revitalization initiative]
-
A.
language revitalization project
chosen
A language revitalization project is an organized, community-centered effort to document, teach, and promote the use of an endangered or marginalized language to ensure its continued transmission and everyday use.
-
B.
language revitalization organization
A language revitalization organization is a group dedicated to preserving, strengthening, and promoting the use of endangered or marginalized languages through education, community programs, documentation, and advocacy.
-
C.
Indigenous knowledge initiative
An Indigenous knowledge initiative is a collaborative effort to recognize, preserve, and apply the traditional knowledge, practices, and cultural wisdom of Indigenous communities in ways that support their self-determination and benefit broader society.
-
D.
Indigenous language
An Indigenous language is a native tongue traditionally spoken by the original inhabitants of a region, embodying their cultural knowledge, identity, and worldview.
-
E.
endangered language
An endangered language is a language at risk of falling out of use, typically because it has few remaining speakers and is not being transmitted to younger generations.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:23 p.m.