Triple
T37837989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michif-Cree |
E943388
|
entity |
| Predicate | usesVerbMorphologyFrom |
P100970
|
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, usesVerbMorphologyFrom, Cree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVerbMorphologyFrom Context triple: [Michif-Cree, usesVerbMorphologyFrom, Cree]
-
A.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
-
B.
hasMorphologicalForm
Indicates that one entity is a specific morphological form or inflected variant of another entity.
-
C.
hasVerbAspect
Indicates that a verb or verbal expression is associated with a particular grammatical aspect (such as perfective, imperfective, or progressive) describing the temporal structure of the action or state.
-
D.
hasVerbalSuffixes
Indicates that a language, word, or grammatical form possesses specific suffixes that are attached to verbs.
-
E.
hasVerbSystemFrom
chosen
Indicates that one language or linguistic system derives or adopts its verb system from another source language or system.
- 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_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.