Triple

T23388022
Position Surface form Disambiguated ID Type / Status
Subject Ruáingga E593936 entity
Predicate hasCommunityEffortsFor P19235 FINISHED
Object language preservation 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: language preservation | Statement: [Ruáingga, hasCommunityEffortsFor, language preservation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunityEffortsFor
Context triple: [Ruáingga, hasCommunityEffortsFor, language preservation]
  • A. hasCommunityEfforts chosen
    Indicates that an entity engages in or is associated with organized activities or initiatives intended to benefit a community.
  • B. hasCommunityDevelopment
    Indicates a relationship where an entity is involved in, supports, or is associated with activities or initiatives aimed at improving and developing a community.
  • C. hasCommunityIn
    Indicates that a community is present, active, or established within a specified location, platform, or context.
  • D. hasCommunityService
    Indicates that an entity is associated with, participates in, or is subject to community service activities or obligations.
  • E. hasCommunityServed
    Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
  • 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a499bad88190afca1afb2e3fddb0 completed April 29, 2026, 6:26 a.m.
PD Predicate disambiguation batch_69f061dde2e481908308952f9c0d3c2e completed April 28, 2026, 7:29 a.m.
Created at: April 17, 2026, 5:35 p.m.