Triple
T5275006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javanese calendar |
E119352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage of Java |
C4934
|
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: cultural heritage of Java Context triple: [Javanese calendar, instanceOf, cultural heritage of Java]
-
A.
Indonesian culture
Indonesian culture is a rich, diverse tapestry of traditions, languages, religions, arts, and social practices shaped by centuries of indigenous heritage and global influences across its many islands.
-
B.
cultural heritage
chosen
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
-
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.
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 historical event
A Javanese historical event is a significant occurrence in the past that took place in Java or involved Javanese people, shaping the island’s political, social, cultural, or religious development.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:51 p.m.