Triple
T4936567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalki |
E110824
|
entity |
| Predicate | cultAndWorship |
P2291
|
FINISHED |
| Object | venerated in some Vaishnava traditions |
—
|
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: venerated in some Vaishnava traditions | Statement: [Kalki, cultAndWorship, venerated in some Vaishnava traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultAndWorship Context triple: [Kalki, cultAndWorship, venerated in some Vaishnava traditions]
-
A.
worshippedIn
chosen
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
B.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to another entity.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
basisOfVeneration
Indicates the reason, quality, or attribute for which something or someone is regarded with reverence or veneration.
-
E.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7085b1dc819099408f6503f0210f |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.