Triple
T5847861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maha Lakshmi Temple, Jhansi |
E129755
|
entity |
| Predicate | hasPrimaryGoddessAspect |
P56384
|
FINISHED |
| Object | Goddess of wealth |
—
|
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: Goddess of wealth | Statement: [Maha Lakshmi Temple, Jhansi, hasPrimaryGoddessAspect, Goddess of wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGoddessAspect Context triple: [Maha Lakshmi Temple, Jhansi, hasPrimaryGoddessAspect, Goddess of wealth]
-
A.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
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.
chosenGoddess
chosen
Indicates that a particular goddess has been selected or designated, typically as a preferred, patron, or special deity in relation to an entity.
-
D.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
E.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.