Triple
T22529555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tat tvam asi |
E556996
|
entity |
| Predicate | functionInTeaching |
P63933
|
FINISHED |
| Object | mahāvākya used for contemplation (nididhyāsana) |
—
|
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: mahāvākya used for contemplation (nididhyāsana) | Statement: [Tat tvam asi, functionInTeaching, mahāvākya used for contemplation (nididhyāsana)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInTeaching Context triple: [Tat tvam asi, functionInTeaching, mahāvākya used for contemplation (nididhyāsana)]
-
A.
teachingFunction
Indicates that one entity serves in a teaching role or performs instructional duties toward others.
-
B.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
C.
typeOfTeaching
Indicates the specific method or style of teaching used in an instructional context.
-
D.
definedTeaching
Indicates that one entity has formally specified or established the teaching content, method, or curriculum for another entity.
-
E.
usesInTeaching
chosen
Indicates that an agent employs a particular resource, method, or material as part of their teaching activities.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed5b5d081909d927f8aee44b673 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.