Triple
T5967212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Īśa Upanishad |
E132781
|
entity |
| Predicate | positionInVeda |
P67110
|
FINISHED |
| Object | final chapter of Śukla Yajurveda Saṃhitā |
—
|
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: final chapter of Śukla Yajurveda Saṃhitā | Statement: [Īśa Upanishad, positionInVeda, final chapter of Śukla Yajurveda Saṃhitā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInVeda Context triple: [Īśa Upanishad, positionInVeda, final chapter of Śukla Yajurveda Saṃhitā]
-
A.
viewOnVedas
Indicates the stance, opinion, or interpretive perspective that one entity holds regarding the Vedas.
-
B.
vedicName
Indicates that an entity is known by a name derived from or used within the Vedic tradition.
-
C.
hasPositionInMahabharata
Indicates that one entity holds or is assigned a specific role, rank, or position within the context of the Mahabharata narrative.
-
D.
associatedUpanishad
Indicates a relationship where something is linked or connected to a particular Upanishad as its source, reference, or context.
-
E.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:03 p.m.