Triple
T23310091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adyghe language |
E590558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | head‑marking language |
C39781
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: head‑marking language Context triple: [Adyghe language, instanceOf, head‑marking language]
-
A.
head-marking language
chosen
A head-marking language is a language in which grammatical relationships within phrases and clauses are primarily indicated by inflection or marking on the central word (the "head") rather than on its dependents.
-
B.
head-final language
A head-final language is a language in which the syntactic head of a phrase (such as a verb, postposition, or noun) typically appears at the end of that phrase, following its complements or modifiers.
-
C.
ergative–absolutive language
An ergative–absolutive language is a language whose grammar groups the subject of an intransitive verb with the object of a transitive verb (absolutive) and treats the subject of a transitive verb differently (ergative), in contrast to nominative–accusative alignment.
-
D.
verb‑initial language
A verb-initial language is a language whose basic, unmarked clause structure places the verb before its core arguments, typically yielding orders such as VSO or VOS.
-
E.
fusional language
A fusional language is a type of language in which single affixes often encode multiple grammatical categories (such as tense, case, number, or gender) simultaneously, making morpheme boundaries less clear-cut.
- F. None of above.
Provenance (1 batch)
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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:05 p.m.