Triple

T23109572
Position Surface form Disambiguated ID Type / Status
Subject former Cree community of Winisk E576276 entity
Predicate preRelocationStatus P150951 FINISHED
Object inhabited Cree community 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: inhabited Cree community | Statement: [former Cree community of Winisk, preRelocationStatus, inhabited Cree community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: preRelocationStatus
Context triple: [former Cree community of Winisk, preRelocationStatus, inhabited Cree community]
  • A. statusAfterRelocation
    Indicates the condition or state an entity has once it has been moved from its original location to a new one.
  • B. relocatedDuring
    Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
  • C. relocationAnnounced
    Indicates that an official communication has been made stating that an entity will move from one location to another.
  • D. relocatedAfter
    Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
  • E. relocatedWithin
    Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
  • F. None of above. chosen

Provenance (4 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_69e245f4af548190898d434a64a1e774 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e0d3d4881908e32837b3fbbb406 completed April 29, 2026, 4:50 a.m.
PD Predicate disambiguation batch_69ef89f020588190b43393e048e7eda3 completed April 27, 2026, 4:08 p.m.
PDg Predicate description generation batch_69ef9b7494f4819088ae59ea3d0ae8ab completed April 27, 2026, 5:23 p.m.
Created at: April 17, 2026, 3:58 p.m.