Triple
T30365425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagamese |
E772407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assamese-based creole |
C56812
|
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: Assamese-based creole Context triple: [Nagamese, instanceOf, Assamese-based creole]
-
A.
Malay-based creole
A Malay-based creole is a stable contact language that developed from Malay as its primary lexical source, mixed with grammatical and lexical influences from other languages, and used as a native or community language.
-
B.
Bantu-based creole
A Bantu-based creole is a contact language that has developed from the interaction of Bantu languages with one or more other languages, featuring a simplified grammar and mixed vocabulary while retaining a core Bantu structural base.
-
C.
Portuguese-based creole
A Portuguese-based creole is a stable, fully developed language that arose from prolonged contact between Portuguese and one or more other languages, incorporating Portuguese-derived vocabulary within a distinct grammatical and phonological system.
-
D.
Arabic-based creole
An Arabic-based creole is a stable, fully developed language that arises from prolonged contact between Arabic and one or more other languages, using Arabic as its primary lexical source while simplifying and restructuring its grammar.
-
E.
Caribbean creole language
A Caribbean creole language is a stable, fully developed natural language that emerged in the Caribbean from the contact and blending of European colonial languages with African, Indigenous, and other linguistic influences.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:58 p.m.