Triple
T18563042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhīṣma Parva |
E453693
|
entity |
| Predicate | includesTeaching |
P131491
|
FINISHED |
| Object | teachings of the Bhagavad Gītā |
—
|
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: teachings of the Bhagavad Gītā | Statement: [Bhīṣma Parva, includesTeaching, teachings of the Bhagavad Gītā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTeaching Context triple: [Bhīṣma Parva, includesTeaching, teachings of the Bhagavad Gītā]
-
A.
containsTeachingOf
chosen
Indicates that one entity includes, embodies, or presents the teaching, doctrine, or instructional content associated with another entity.
-
B.
hasTeaching
Indicates that one entity provides instruction or educational guidance to another entity.
-
C.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
D.
usesInTeaching
Indicates that an agent employs a particular resource, method, or material as part of their teaching activities.
-
E.
definedTeaching
Indicates that one entity has formally specified or established the teaching content, method, or curriculum for another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afb4f088190adf0b2b64057a210 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.