Triple
T26508925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadyojata |
E669625
|
entity |
| Predicate | associatedWithMantra |
P101725
|
FINISHED |
| Object | Sadyojata mantra |
—
|
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: Sadyojata mantra | Statement: [Sadyojata, associatedWithMantra, Sadyojata mantra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMantra Context triple: [Sadyojata, associatedWithMantra, Sadyojata mantra]
-
A.
associatedWithYogi
Indicates a relationship in which an entity has a connection, link, or involvement with a yogi.
-
B.
associatedWithMahavakya
Indicates a relationship in which something is connected or related to a Mahavakya (a great Vedic or Upanishadic saying), typically by expressing, embodying, or being derived from it.
-
C.
associatedWithTattva
Indicates a relationship in which something is linked or connected to a specific tattva (fundamental principle or element) within a conceptual or philosophical system.
-
D.
mantraText
chosen
Indicates that a mantra is associated with a specific textual content or wording.
-
E.
possessedMantraFrom
Indicates that one entity had ownership or control of a particular mantra originating from another entity or source.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 27, 2026, 1:18 a.m.