Triple
T26840985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasak script |
E675774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indonesian script |
C52107
|
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: Indonesian script Context triple: [Sasak script, instanceOf, Indonesian script]
-
A.
Javanese script
Javanese script is an abugida writing system traditionally used on the island of Java to write the Javanese language, characterized by its rounded, ornamental characters and complex orthographic rules.
-
B.
indigenous Philippine script
An indigenous Philippine script is a traditional writing system developed by native Filipino ethnolinguistic groups, historically used to record their languages, culture, and knowledge before and alongside colonial influences.
-
C.
Zhuang script
Zhuang script is the writing system used for the Zhuang language, historically based on modified Chinese characters (Sawndip) and now primarily written with a standardized Latin-based alphabet.
-
D.
Old Javanese inscription
An Old Javanese inscription is a historical text carved or written in the Old Javanese language, typically on stone, metal, or other durable materials, documenting political, religious, legal, or social matters in ancient Java.
-
E.
Javanese calendrical system
The Javanese calendrical system is a syncretic timekeeping framework that combines elements of Hindu-Buddhist, Islamic, and indigenous Javanese traditions into a complex cycle of solar, lunar, and five-day market weeks used for ritual, agricultural, and social purposes.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:08 a.m.