Triple
T21258999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru |
E523945
|
entity |
| Predicate | importantInScripture |
P11163
|
FINISHED |
| Object | Bhagavad Gita commentarial traditions |
—
|
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: Bhagavad Gita commentarial traditions | Statement: [Guru, importantInScripture, Bhagavad Gita commentarial traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantInScripture Context triple: [Guru, importantInScripture, Bhagavad Gita commentarial traditions]
-
A.
importantHymn
Indicates that a hymn holds significant importance or prominence within a particular religious, cultural, or musical context.
-
B.
inScripture
chosen
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
C.
positionInScripture
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
D.
scripturalUse
Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
-
E.
relevanceToBiblicalStudies
Indicates that something has significance, usefulness, or meaningful connection to the study, interpretation, or understanding of the Bible and related scholarship.
- F. None of above.
Provenance (3 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.