Triple
T31078054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opalia |
E792024
|
entity |
| Predicate | deityRoleOfOps |
P118406
|
FINISHED |
| Object | provider of abundance |
—
|
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: provider of abundance | Statement: [Opalia, deityRoleOfOps, provider of abundance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityRoleOfOps Context triple: [Opalia, deityRoleOfOps, provider of abundance]
-
A.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
B.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
deityDomain
Indicates that a deity has authority, influence, or primary association over a particular domain, aspect, or sphere of existence.
-
D.
coreDeitiesInvoked
Indicates that the primary or central deities of a tradition are explicitly called upon, referenced, or appealed to in a given context or act.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bbbaa081909fb1aa003e864c08 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.