Triple
T18593389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savita |
E454425
|
entity |
| Predicate | roleInGayatriMantra |
P132709
|
FINISHED |
| Object | deity to whom the mantra is addressed |
—
|
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: deity to whom the mantra is addressed | Statement: [Savita, roleInGayatriMantra, deity to whom the mantra is addressed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGayatriMantra Context triple: [Savita, roleInGayatriMantra, deity to whom the mantra is addressed]
-
A.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
B.
roleInSikhTradition
Indicates the specific function, status, or position an entity holds within Sikh religious, cultural, or historical practices and institutions.
-
C.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
D.
BrahmaSutrasRole
Indicates the specific interpretive or doctrinal role that an entity plays in relation to the Brahma Sutras.
-
E.
portraysPurushaAs
Indicates that one entity represents or depicts another entity as Purusha, the cosmic or primordial being.
- F. None of above. chosen
Provenance (4 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b7ce3881908302ee27a2cf80d6 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.