Triple
T32054351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamakshi |
E818573
|
entity |
| Predicate | hasMantraTradition |
P129880
|
FINISHED |
| Object | Sri Vidya mantras |
—
|
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: Sri Vidya mantras | Statement: [Kamakshi, hasMantraTradition, Sri Vidya mantras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMantraTradition Context triple: [Kamakshi, hasMantraTradition, Sri Vidya mantras]
-
A.
hasMantraStyle
Indicates a relationship where an entity is associated with or characterized by a particular style or form of mantra.
-
B.
mantraText
Indicates that a mantra is associated with a specific textual content or wording.
-
C.
possessedMantraFrom
Indicates that one entity had ownership or control of a particular mantra originating from another entity or source.
-
D.
belongsToMacroTradition
chosen
Indicates that one entity is classified as part of, or originating from, a broader overarching tradition or school.
-
E.
guruInTradition
Indicates that one entity serves as a spiritual teacher or guide (guru) within the lineage, school, or religious tradition represented by the other 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: May 1, 2026, 12:21 a.m.