Triple

T26815273
Position Surface form Disambiguated ID Type / Status
Subject Schefferville E672107 entity
Predicate nearbyIndigenousCommunities P73263 FINISHED
Object Matimekush-Lac John NE NERFINISHED

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: Matimekush-Lac John | Statement: [Schefferville, nearbyIndigenousCommunities, Matimekush-Lac John]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyIndigenousCommunities
Context triple: [Schefferville, nearbyIndigenousCommunities, Matimekush-Lac John]
  • A. nearbyIndigenousHeritage
    Indicates that an entity is located close to a site, area, or feature of Indigenous cultural, historical, or spiritual heritage.
  • B. traditionalTerritoryNearby
    Indicates that one entity is located close to the traditional territory associated with another entity.
  • C. indigenousCommunity
    Indicates that an entity is an indigenous community, i.e., a group with historical, cultural, and ancestral ties to a specific territory predating external or colonial societies.
  • D. nearbyNativeGroups chosen
    Indicates that there are indigenous or native groups located in close geographic proximity to the referenced entity.
  • E. nearTribalGroup
    Indicates that one entity is located geographically close to a tribal group.
  • 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_69eeb3225a3c8190aaf6746efeded2f3 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f71f8ee0688190bd025f27993452d3 completed May 3, 2026, 10:12 a.m.
PD Predicate disambiguation batch_69f71cc405c08190863565609a4c8499 completed May 3, 2026, 10 a.m.
Created at: April 27, 2026, 4:31 a.m.