Triple
T6892621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiradjeri |
E159082
|
entity |
| Predicate | hasLanguageRevivalPrograms |
P4252
|
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: [Wiradjeri, hasLanguageRevivalPrograms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageRevivalPrograms Context triple: [Wiradjeri, hasLanguageRevivalPrograms, yes]
-
A.
hasLanguageRevitalizationEfforts
chosen
Indicates that there are organized actions or initiatives aimed at preserving, strengthening, or reviving the use of a particular language.
-
B.
languageRevived
Indicates that a previously endangered or no-longer-spoken language has been brought back into active use within a community.
-
C.
languageRevivalMethod
Indicates the method or strategy used to revive or revitalize a language that is endangered, dormant, or no longer actively spoken.
-
D.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
E.
hasNationalLanguageRegulator
Indicates that an entity has an official body or authority responsible for regulating and overseeing its national language.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d930ab548190953291d63cbc721b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.