Triple
T8313792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mithras |
E194653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Iranian god |
C16283
|
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: Indo-Iranian god Context triple: [Mithras, instanceOf, Indo-Iranian god]
-
A.
Indo-Iranian deity
chosen
An Indo-Iranian deity is a divine figure originating from the shared religious and mythological traditions of the ancient Indo-Aryan and Iranian peoples, often associated with natural forces, social order, and cosmic principles.
-
B.
Anatolian deity
An Anatolian deity is a divine figure worshiped in the ancient regions of Anatolia, embodying local religious beliefs, natural forces, or societal roles within the mythologies of cultures such as the Hittites, Luwians, and Phrygians.
-
C.
Babylonian god
A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
-
D.
Indo-European religion
Indo-European religion refers to the reconstructed set of mythological beliefs, rituals, and deities shared by the ancient peoples speaking Proto-Indo-European languages, inferred from common patterns across their descendant traditions.
-
E.
Etruscan god
An Etruscan god is a divine being from the ancient Etruscan religion, associated with specific aspects of nature, fate, or human activity and often later syncretized with Greek and Roman deities.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:55 p.m.