Triple
T22782132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cree Nations of Ontario |
E563867
|
entity |
| Predicate | hasContemporaryIssues |
P76511
|
FINISHED |
| Object | land rights |
—
|
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: land rights | Statement: [Cree Nations of Ontario, hasContemporaryIssues, land rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryIssues Context triple: [Cree Nations of Ontario, hasContemporaryIssues, land rights]
-
A.
notableModernIssue
chosen
Indicates that the subject is recognized as a significant or widely discussed issue in contemporary times.
-
B.
hasNotableContemporary
Indicates that one entity is recognized as a significant or prominent contemporary (living or active in the same period) of another entity.
-
C.
modernIssue
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
D.
hasModernRelevance
Indicates that something maintains significance, applicability, or impact in contemporary times or current contexts.
-
E.
contemporaryEvents
Indicates that two or more events occur in the same time period or overlap temporally.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2dd250819093a5c49806916ec4 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.