Triple
T9483963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colloquial Singaporean English |
E228714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Singaporean English variety |
C2257
|
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: Singaporean English variety Context triple: [Colloquial Singaporean English, instanceOf, Singaporean English variety]
-
A.
regional variety of Indian English
A regional variety of Indian English is a localized form of English spoken in a specific part of India, shaped by the region’s native languages, cultural norms, and pronunciation patterns.
-
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.
national variety of English
chosen
A national variety of English is a distinct form of the English language associated with a particular country, characterized by its own norms of pronunciation, vocabulary, grammar, and usage.
-
D.
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.
-
E.
regional variety of the Javanese language
A regional variety of the Javanese language is a geographically distinct form of Javanese characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Javanese varieties.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:55 p.m.