Triple
T34940182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yu Gong |
E1007693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in Chinese folklore |
C25075
|
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: character in Chinese folklore Context triple: [Yu Gong, instanceOf, character in Chinese folklore]
-
A.
Chinese folk deity
chosen
A Chinese folk deity is a supernatural being venerated in Chinese popular religion, often associated with local legends, ancestral spirits, or personified natural forces, and worshipped for protection, blessings, and guidance in daily life.
-
B.
Chinese legend
A Chinese legend is a traditional narrative from Chinese culture that blends historical events, folklore, mythology, and moral lessons, passed down through generations to explain the world and convey cultural values.
-
C.
characters in English folklore
Characters in English folklore are the legendary figures, both human and supernatural, that populate traditional English tales, myths, and ballads, embodying cultural values, fears, and imaginations passed down through generations.
-
D.
Japanese folk hero
A Japanese folk hero is a legendary or semi-legendary figure from Japanese tradition whose extraordinary deeds, virtues, or cleverness embody cultural values and inspire popular stories, songs, and festivals.
-
E.
Slavic folklore character
A Slavic folklore character is a mythic or legendary figure from Slavic traditions, embodying cultural values, fears, and natural forces through tales of magic, morality, and the supernatural.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.