Triple
T20703607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayisi Dene First Nation |
E508842
|
entity |
| Predicate | relocationConsequences |
P60840
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Sayisi Dene First Nation, relocationConsequences, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationConsequences Context triple: [Sayisi Dene First Nation, relocationConsequences, poverty]
-
A.
relocationResultedIn
chosen
Indicates that one relocation event caused or led to a particular outcome, state, or consequence.
-
B.
relocationBy
Indicates that one entity causes or performs the movement or transfer of another entity from one location to another.
-
C.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
D.
requiredRelocationFrom
Indicates that one entity mandates or necessitates the relocation of another entity away from a specified source location or context.
-
E.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18dbda081908217dcb61cbf7ba4 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.