Triple
T34085423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varalakshmi Vratam |
E874164
|
entity |
| Predicate | honorsAspectOfLakshmi |
P60804
|
FINISHED |
| Object | Varalakshmi |
—
|
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: Varalakshmi | Statement: [Varalakshmi Vratam, honorsAspectOfLakshmi, Varalakshmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsAspectOfLakshmi Context triple: [Varalakshmi Vratam, honorsAspectOfLakshmi, Varalakshmi]
-
A.
honorsAspectOf
chosen
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
B.
hasViewOnLakshmi
Indicates that an entity holds an opinion, perspective, or stance regarding Lakshmi.
-
C.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
-
D.
honorsNimbarkaAs
Indicates that someone regards Nimbarka with a particular status, role, or title, such as a teacher, authority, or incarnation.
-
E.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:52 a.m.