Triple
T37838013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michif-Cree |
E943388
|
entity |
| Predicate | hasLexiconInfluenceFrom |
P9129
|
FINISHED |
| Object | Cree |
—
|
NE NERFINISHED |
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: Cree | Statement: [Michif-Cree, hasLexiconInfluenceFrom, Cree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLexiconInfluenceFrom Context triple: [Michif-Cree, hasLexiconInfluenceFrom, Cree]
-
A.
hasLexicalInfluenceOn
chosen
Indicates that one linguistic element (such as a word, phrase, or lexicon) has affected or shaped the form, usage, or meaning of another linguistic element.
-
B.
hasGrammarInfluencedBy
Indicates that the grammatical structure or rules of one language or system are shaped or affected by the grammar of another.
-
C.
languageInfluence
Indicates that one language has an effect on the development, usage, or characteristics of another language.
-
D.
languageOfInfluence
Indicates a relationship where one language has influenced the development, usage, or characteristics of another language.
-
E.
hasLexiconSource
Indicates that a lexical item or entry is derived from, documented in, or otherwise sourced from a particular lexicon or lexical resource.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:19 p.m.