Triple
T3109134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naskapi language |
E64906
|
entity |
| Predicate | statusInCanada |
P33447
|
FINISHED |
| Object | Indigenous minority language |
—
|
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: Indigenous minority language | Statement: [Naskapi language, statusInCanada, Indigenous minority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInCanada Context triple: [Naskapi language, statusInCanada, Indigenous minority language]
-
A.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
B.
countrySpecificStatus
chosen
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
C.
statusInRegion
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
D.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
E.
statusInFrance
Indicates the legal, social, or official standing or condition that an entity has within the jurisdiction of France.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada2a0ab2481908db50738ec3ad0fb |
completed | March 8, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.