Triple
T17096467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahabharata tradition in Java |
E414863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Javanese Hindu tradition |
C5737
|
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 Hindu tradition Context triple: [Mahabharata tradition in Java, instanceOf, Javanese Hindu tradition]
-
A.
Indonesian culture
chosen
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.
prophet in Javanese tradition
A prophet in Javanese tradition is a spiritually enlightened figure who mediates between the divine and the human world, guiding communities through sacred wisdom, moral teachings, and mystical insight often blended with local cultural beliefs.
-
C.
Javanese dynasty
A Javanese dynasty is a ruling lineage or royal house originating from the island of Java, Indonesia, that holds political, cultural, and spiritual authority over a Javanese kingdom or realm across generations.
-
D.
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.
-
E.
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.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.