Triple
T22140881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao E |
E547153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese legendary figure |
C37777
|
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: Chinese legendary figure Context triple: [Cao E, instanceOf, Chinese legendary figure]
-
A.
Chinese legend
chosen
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.
-
B.
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.
-
C.
Chinese folk deity
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.
-
D.
Chinese military figure
A Chinese military figure is an individual from any period of Chinese history who holds or has held a position of command, leadership, or strategic influence within China’s armed forces or military institutions.
-
E.
ancient Chinese person
An ancient Chinese person is an individual who lived in historical China, shaped by its dynastic rule, philosophical traditions like Confucianism and Daoism, and distinctive cultural practices, technologies, and social structures of the time.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.