Triple
T7171954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nukulaelae dialect |
E167220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Tuvaluan |
C20904
|
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: regional variety of Tuvaluan Context triple: [Nukulaelae dialect, instanceOf, regional variety of Tuvaluan]
-
A.
variety of Tongan language
A variety of Tongan language is a distinct form or dialect of Tongan characterized by unique phonological, lexical, or grammatical features associated with a particular region, community, or social group.
-
B.
Chuukic language
The Chuukic language is a group of closely related Micronesian languages spoken primarily in the Chuuk State of the Federated States of Micronesia and surrounding regions, characterized by shared phonological and grammatical features within the Oceanic branch of the Austronesian language family.
-
C.
variety of Marshallese language
A variety of Marshallese language is a distinct regional or social form of Marshallese characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other forms.
-
D.
Nicobarese language variety
A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
-
E.
Ivatan language variety
A specific form or dialect of the Ivatan language, characterized by its unique phonological, lexical, and grammatical features within the Ivatan-speaking community.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:48 p.m.