Triple
T26865457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Tanna |
E676453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Lenakel language |
C52141
|
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: variety of Lenakel language Context triple: [South Tanna, instanceOf, variety of Lenakel language]
-
A.
variety of Lau language
A variety of Lau language is a distinct regional or social form of the Lau language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Lau forms.
-
B.
Akan language variety
A specific form or dialect of the Akan language, distinguished by its unique phonological, lexical, and grammatical features used by a particular regional or social group.
-
C.
variety of the Kayan language
A variety of the Kayan language is a distinct regional or social form of Kayan characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Kayan varieties.
-
D.
Kayan language variety
A Kayan language variety is a specific linguistic form or dialect within the Kayan language family, spoken by Kayan communities and characterized by its own phonological, lexical, and grammatical features.
-
E.
variety of the Okinawan language
A variety of the Okinawan language is a distinct regional or social form of Okinawan characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Okinawan varieties.
- F. None of above. chosen
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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:28 a.m.