Triple
T30462850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Iranian mythology |
E775057
|
entity |
| Predicate | sharesDeityCognate |
P126907
|
FINISHED |
| Object | Mitra–Mithra complex |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mitra–Mithra complex | Statement: [Indo-Iranian mythology, sharesDeityCognate, Mitra–Mithra complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDeityCognate Context triple: [Indo-Iranian mythology, sharesDeityCognate, Mitra–Mithra complex]
-
A.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
B.
hasSyncreticDeity
Indicates that one deity is a composite or fusion of multiple distinct deities, combining their attributes or identities into a single syncretic figure.
-
C.
relatedDeityFamily
Indicates a familial relationship between a deity and another entity, such as being a parent, child, sibling, or spouse within a divine family.
-
D.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
E.
comparableDeity
chosen
Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
- F. None of above.
Provenance (3 batches)
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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:10 p.m.