Triple
T21938594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kristang language |
E541757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malacca Portuguese Creole |
C6464
|
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: Malacca Portuguese Creole Context triple: [Kristang language, instanceOf, Malacca Portuguese Creole]
-
A.
Minahasan language
The Minahasan language is an Austronesian language (or group of closely related dialects) traditionally spoken by the Minahasan people of North Sulawesi, Indonesia, characterized by complex verbal morphology and significant influence from Malay/Indonesian.
-
B.
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.
-
C.
Beja language
The Beja language is an Afroasiatic Cushitic language spoken primarily by the Beja people across parts of Sudan, Egypt, and Eritrea, notable for its conservative linguistic features and limited written tradition.
-
D.
Portuguese-based creole
chosen
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.
-
E.
regional Malay dialect
A regional Malay dialect is a localized variety of the Malay language characterized by distinct phonological, lexical, and grammatical features shaped by the specific geographic, historical, and cultural context of its speakers.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:55 p.m.