Triple
T5845845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bṛhadāraṇyaka Upanishad |
E129707
|
entity |
| Predicate | famousMahāvākya |
P21579
|
FINISHED |
| Object | ahaṃ brahmāsmi |
—
|
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: ahaṃ brahmāsmi | Statement: [Bṛhadāraṇyaka Upanishad, famousMahāvākya, ahaṃ brahmāsmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousMahāvākya Context triple: [Bṛhadāraṇyaka Upanishad, famousMahāvākya, ahaṃ brahmāsmi]
-
A.
associatedUpanishad
chosen
Indicates a relationship where something is linked or connected to a particular Upanishad as its source, reference, or context.
-
B.
identifiesBrahmanWith
Indicates that one entity asserts, recognizes, or treats another entity as being identical with or the same as Brahman (the ultimate reality in certain Indian philosophical traditions).
-
C.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
-
D.
attainedKevalaJnana
Indicates that an entity has achieved Kevala Jnana, the state of absolute or perfect knowledge.
-
E.
placeOfEnlightenment
Indicates the location or setting where an entity attains spiritual or intellectual enlightenment.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.