Triple
T18540213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badarayana |
E453074
|
entity |
| Predicate | BrahmaSutrasSubject |
P76118
|
FINISHED |
| Object | nature of Brahman |
—
|
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: nature of Brahman | Statement: [Badarayana, BrahmaSutrasSubject, nature of Brahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrahmaSutrasSubject Context triple: [Badarayana, BrahmaSutrasSubject, nature of Brahman]
-
A.
associatedUpanishad
Indicates a relationship where something is linked or connected to a particular Upanishad as its source, reference, or context.
-
B.
numberOfSutras
Indicates the quantity or count of sutras associated with a given entity.
-
C.
teachesRelationBetweenBrahmanAndSoulsAs
chosen
Indicates that a subject teaches or explains the nature of the relationship between Brahman and individual souls in a specified manner.
-
D.
meditationSubject
Indicates that one entity is the topic, focus, or object upon which another entity meditates.
-
E.
viewOnVedas
Indicates the stance, opinion, or interpretive perspective that one entity holds regarding the Vedas.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b64178819082861a03fd067095 |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.