Triple
T29915659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundanese chronicles |
E759789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sundanese literature |
C56527
|
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: Sundanese literature Context triple: [Sundanese chronicles, instanceOf, Sundanese literature]
-
A.
Javanese writer
A Javanese writer is an author of literary or scholarly works who is ethnically Javanese or writes primarily in the Javanese language, often engaging with Javanese culture, history, and social issues.
-
B.
Bugis literature
Bugis literature encompasses the oral and written works of the Bugis people of South Sulawesi, Indonesia, including epic poems, historical chronicles, myths, and religious texts traditionally composed in the Bugis language and script.
-
C.
Bangladeshi literature
Bangladeshi literature encompasses the body of written and oral works produced in Bangladesh and by Bangladeshi authors, primarily in Bengali and English, reflecting the region’s history, culture, politics, and social realities.
-
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.
Burmese literature
Burmese literature is the body of written and oral works produced in the Burmese language and related languages of Myanmar, reflecting the country’s religious traditions, historical experiences, and diverse ethnic cultures from classical court poetry to contemporary fiction.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:12 p.m.