Triple
T4186239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawi language |
E88318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Javanese language |
C967
|
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: Old Javanese language Context triple: [Kawi language, instanceOf, Old Javanese language]
-
A.
Austronesian language
chosen
An Austronesian language is any member of a large family of languages spoken from Madagascar across Island Southeast Asia and the Pacific to Easter Island, characterized by shared phonological, grammatical, and lexical features tracing back to a common ancestral tongue.
-
B.
Tai language
A Tai language is a member of the Tai branch of the Kra–Dai language family, characterized by tonal phonology and analytic grammar, spoken primarily in Southeast Asia by Tai ethnic groups.
-
C.
Dravidian language
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
-
D.
Bikol language
The Bikol language is an Austronesian language (or group of closely related languages) spoken primarily in the Bicol Region of the Philippines, known for its distinct phonology and vocabulary while sharing many features with other Central Philippine languages.
-
E.
Japonic languages
Japonic languages are a small language family native to Japan and nearby regions, including Japanese and the Ryukyuan languages, characterized by shared grammatical structures and historical origins.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.