Triple
T23623108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta Indonesian |
E583376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Indonesian language |
C47881
|
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 Indonesian language Context triple: [Jakarta Indonesian, instanceOf, variety of Indonesian language]
-
A.
regional language of Indonesia
A regional language of Indonesia is a native language spoken by a specific ethnic group or community within the Indonesian archipelago, distinct from the national language Bahasa Indonesia and used in local daily communication, culture, and traditions.
-
B.
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.
-
C.
Indonesian word
An Indonesian word is a basic linguistic unit in the Indonesian language that carries meaning and can function independently or as part of larger expressions in communication.
-
D.
Sambal language variety
Sambal language variety is a specific form or dialect of the Sambal language, characterized by distinct phonological, lexical, and grammatical features used by a particular Sambal-speaking community.
-
E.
regional variety of the Sasak language
A regional variety of the Sasak language is a geographically and socially distinct form of Sasak characterized by systematic differences in pronunciation, vocabulary, and grammar from other Sasak 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:46 p.m.