Triple
T21145769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabataean religion |
E521049
|
entity |
| Predicate | hasKeyDeityRole |
P98641
|
FINISHED |
| Object | Dushara as chief god |
—
|
LITERAL FINISHED |
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: Dushara as chief god | Statement: [Nabataean religion, hasKeyDeityRole, Dushara as chief god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyDeityRole Context triple: [Nabataean religion, hasKeyDeityRole, Dushara as chief god]
-
A.
hasSupremeDeityRole
chosen
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
B.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
C.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
hasDeityGroup
Indicates a relationship where an entity is associated with, or belongs to, a particular group or pantheon of deities.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fcdb7c8190ae04d6ad9dff3187 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.