Triple
T6339481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taittirīya Upanishad |
E142586
|
entity |
| Predicate | BhṛguvallīFocus |
P70070
|
FINISHED |
| Object | story of Bhṛgu and Varuṇa |
—
|
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: story of Bhṛgu and Varuṇa | Statement: [Taittirīya Upanishad, BhṛguvallīFocus, story of Bhṛgu and Varuṇa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BhṛguvallīFocus Context triple: [Taittirīya Upanishad, BhṛguvallīFocus, story of Bhṛgu and Varuṇa]
-
A.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
-
B.
NirguniLavaniFocus
Indicates a focus on the performance, style, or thematic elements of Nirguni Lavani within a relationship or context.
-
C.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
D.
viewOnVedas
Indicates the stance, opinion, or interpretive perspective that one entity holds regarding the Vedas.
-
E.
दोषसिद्धि
Indicates a judicial relationship where an authority formally establishes and declares a person’s guilt for an alleged offense.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654fb774819087bffb8b966a790a |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:30 p.m.