Triple

T15823248
Position Surface form Disambiguated ID Type / Status
Subject Northern Embera language E383664 entity
Predicate vitalityConcern P65850 FINISHED
Object subject to language shift toward Spanish in some communities 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: subject to language shift toward Spanish in some communities | Statement: [Northern Embera language, vitalityConcern, subject to language shift toward Spanish in some communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vitalityConcern
Context triple: [Northern Embera language, vitalityConcern, subject to language shift toward Spanish in some communities]
  • A. hasHealthConcern
    Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
  • B. concernsProblem chosen
    Indicates that something is about, related to, or deals with a particular problem or issue.
  • C. concernsMeasure
    Indicates that something is about or relates specifically to a particular quantitative measure or measurement.
  • D. concernsTitle
    Indicates that something is about or relates specifically to a particular title (such as a name, designation, or formal heading).
  • E. concern
    Indicates that one entity is about, relates to, or is of interest or importance to another entity.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a96b848190845cf547034a24f2 completed April 16, 2026, 11:14 a.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.