Triple
T22279169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitreyi Brāhmaṇa |
E550685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Upanishadic text section |
C42540
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Upanishadic text section Context triple: [Maitreyi Brāhmaṇa, instanceOf, Upanishadic text section]
-
A.
Vedantic treatise
A Vedantic treatise is a systematic philosophical work that explicates, analyzes, and interprets the core metaphysical, epistemological, and spiritual doctrines of Vedanta, often through commentary on foundational scriptures like the Upanishads, Bhagavad Gita, and Brahma Sutras.
-
B.
Upanishads collection
chosen
A curated set of ancient Indian philosophical texts from the Upanishads, organized for study, reference, and comparative exploration of their teachings.
-
C.
Samkhya text
A Samkhya text is a philosophical work rooted in the ancient Indian Samkhya system that systematically analyzes reality through the dual principles of purusha (consciousness) and prakriti (primordial matter) to explain cosmology, psychology, and liberation.
-
D.
Hindu religious texts
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
E.
Hindu technical scripture
A Hindu technical scripture is a specialized sacred text that systematically presents practical knowledge—such as ritual procedures, architecture, arts, sciences, or governance—within a Hindu religious and philosophical framework.
- F. None of above.
Provenance (1 batch)
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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:40 p.m.