Triple
T26725983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prabhavakacarita |
E673836
|
entity |
| Predicate | illustratesDoctrine |
P162355
|
FINISHED |
| Object | right knowledge |
—
|
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: right knowledge | Statement: [Prabhavakacarita, illustratesDoctrine, right knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illustratesDoctrine Context triple: [Prabhavakacarita, illustratesDoctrine, right knowledge]
-
A.
illustratesDoctrine
chosen
Indicates that one entity serves as an example or demonstration that clarifies, explains, or supports a particular doctrine or set of principles in another entity.
-
B.
teachesDoctrine
Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
-
C.
examinesDoctrine
Indicates that one entity critically studies, analyzes, or evaluates a particular doctrine or set of beliefs.
-
D.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:42 a.m.