Triple
T27341745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihat Jataka |
E684122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu astrological text |
C52739
|
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: Hindu astrological text Context triple: [Brihat Jataka, instanceOf, Hindu astrological text]
-
A.
Hindu astronomical work
A Hindu astronomical work is a traditional Indian text that systematically describes celestial bodies, their motions, and related mathematical and calendrical calculations within the framework of Hindu cosmology.
-
B.
Ayurvedic text
An Ayurvedic text is a traditional manuscript or written work that systematically presents the principles, practices, and remedies of Ayurveda for maintaining health and treating disease.
-
C.
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.
-
D.
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.
-
E.
Hindu astrology system
A Hindu astrology system is a traditional framework that interprets the positions and movements of celestial bodies to understand human life, destiny, and cosmic influences according to Vedic philosophical principles.
- F. None of above. chosen
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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:43 a.m.