Triple
T10065003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guandi |
E213077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese folk religion deity |
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: Chinese folk religion deity Context triple: [Guandi, instanceOf, Chinese folk religion deity]
-
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.
Vietnamese folk deities
Vietnamese folk deities are a diverse pantheon of indigenous, ancestral, nature, and historical spirits venerated through syncretic rituals that blend Buddhism, Taoism, Confucianism, and local animist traditions to protect communities and guide daily life.
-
C.
Vietnamese folk religious concept
A Vietnamese folk religious concept is a culturally rooted belief, practice, or spiritual entity within Vietnam’s indigenous, syncretic tradition that blends ancestor veneration, local deities, and elements of Buddhism, Taoism, and Confucianism.
-
D.
Native American deity
A Native American deity is a supernatural being revered within Indigenous cultures of the Americas, often embodying natural forces, ancestral spirits, or cultural principles and playing a central role in creation stories, rituals, and moral teachings.
-
E.
deity
A deity is a supernatural being, often worshiped or revered, believed to possess powers beyond those of humans and to influence the universe or aspects of life.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 8:58 p.m.