Triple
T35227106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maiya |
E1017127
|
entity |
| Predicate | invokesDeityType |
P141496
|
FINISHED |
| Object | Shakti |
—
|
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: Shakti | Statement: [Maiya, invokesDeityType, Shakti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokesDeityType Context triple: [Maiya, invokesDeityType, Shakti]
-
A.
coreDeitiesInvoked
chosen
Indicates that the primary or central deities of a tradition are explicitly called upon, referenced, or appealed to in a given context or act.
-
B.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
C.
involvesDeity
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
D.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
E.
refersToDeityFunction
Indicates that one entity denotes, describes, or points to the role, power, or functional aspect of a deity.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.