Triple
T11305013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interior Salish peoples |
E267691
|
entity |
| Predicate | contemporaryStatus |
P28747
|
FINISHED |
| Object | recognized as First Nations in Canada |
—
|
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: recognized as First Nations in Canada | Statement: [Interior Salish peoples, contemporaryStatus, recognized as First Nations in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryStatus Context triple: [Interior Salish peoples, contemporaryStatus, recognized as First Nations in Canada]
-
A.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
B.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
C.
modernStatus
chosen
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
D.
contemporaryReception
Indicates how a work, event, or figure was received, perceived, or evaluated by audiences and critics at the time it originally appeared or occurred.
-
E.
contemporaryWith
Indicates that two entities existed, occurred, or were active during the same time period.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.