Triple
T14258188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tłı̨chǫ language |
E353438
|
entity |
| Predicate | isPolysynthetic |
P113469
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Tłı̨chǫ language, isPolysynthetic, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPolysynthetic Context triple: [Tłı̨chǫ language, isPolysynthetic, Yes]
-
A.
areAgglutinativeLanguages
Indicates that the related languages primarily form words by stringing together distinct morphemes, each carrying a specific grammatical meaning, in a clear and segmentable way.
-
B.
compositionalForm
Indicates the structural or formal composition that defines how parts are organized or combined within something.
-
C.
isInflectedLanguage
Indicates that a language uses systematic changes in word form (inflections) to express grammatical categories such as tense, case, number, or gender.
-
D.
polymorphic
Indicates that an entity can take on multiple distinct forms or types while maintaining a common interface or role in a relationship or action.
-
E.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
- F. None of above. chosen
Provenance (4 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6352611c819090d062fe3079cd03 |
completed | April 14, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.