Triple

T408809
Position Surface form Disambiguated ID Type / Status
Subject Tlingit E9440 entity
Predicate hasRevitalizationEffort P4252 FINISHED
Object community language classes 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: community language classes | Statement: [Tlingit, hasRevitalizationEffort, community language classes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRevitalizationEffort
Context triple: [Tlingit, hasRevitalizationEffort, community language classes]
  • A. revitalizationEffort
    Indicates efforts or actions undertaken to restore, renew, or improve the condition, vitality, or functionality of something.
  • B. hasReformEffort
    Indicates that an entity undertakes, is involved in, or is the subject of a deliberate effort to change, improve, or restructure a system, policy, or practice.
  • C. hasLanguageRevitalizationEfforts chosen
    Indicates that there are organized actions or initiatives aimed at preserving, strengthening, or reviving the use of a particular language.
  • D. revival
    Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
  • E. hasStandardizationEffort
    Indicates that there is an organized effort or process to standardize something, such as practices, formats, or specifications, across relevant entities or contexts.
  • 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_69a2e80111fc8190961d5b7c6154123f completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ecbf0650819080753815ca280eec completed Feb. 28, 2026, 1:25 p.m.
PD Predicate disambiguation batch_69a2e971a3a481909e6b075f25dd234a completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.