Triple
T31665145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongbieocheonga |
E808104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Korean literature |
C57847
|
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: classical Korean literature Context triple: [Yongbieocheonga, instanceOf, classical Korean literature]
-
A.
classical literature
Classical literature encompasses the enduring works of ancient Greek and Roman authors, as well as later canonical texts, that have significantly shaped Western thought, art, and literary tradition.
-
B.
Korean poetic work
chosen
A Korean poetic work is a literary composition written in the Korean language that uses rhythm, imagery, and traditional or modern poetic forms (such as sijo, gasa, or free verse) to express emotions, ideas, or narratives.
-
C.
classical Tamil literature
Classical Tamil literature encompasses the ancient poetic, philosophical, and didactic works composed primarily between 300 BCE and 300 CE in Tamil, including the Sangam corpus and later ethical and devotional texts that shaped South Indian culture and thought.
-
D.
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.
-
E.
Japanese literature period
A Japanese literature period is a distinct historical era in Japan characterized by its prevailing literary forms, themes, languages, and cultural influences that shape the production and reception of written works.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:59 p.m.