Triple
T16889598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanacaraka |
E421631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Javanese script |
C37715
|
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: Javanese script Context triple: [Hanacaraka, instanceOf, Javanese script]
-
A.
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.
-
B.
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.
-
C.
ancient Javanese inscription
An ancient Javanese inscription is a historical text carved or written in Old Javanese script on durable materials such as stone, metal, or clay, documenting religious, political, legal, or cultural aspects of early Javanese civilization.
-
D.
Javanese historical text
A Javanese historical text is a written work, often in Old or Middle Javanese script and language, that records, interprets, or mythologizes past events, rulers, and cultural developments of Javanese society.
-
E.
Osage-language writing system
The Osage-language writing system is a modern, standardized orthography, including a unique alphabet, designed specifically to represent the sounds and structure of the Osage language accurately and support its revitalization.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.