Triple
T30750042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassapa Buddha |
E782930
|
entity |
| Predicate | kalpa |
P169632
|
FINISHED |
| Object | Bhaddakappa (Auspicious Aeon) |
—
|
NE NERFINISHED |
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: Bhaddakappa (Auspicious Aeon) | Statement: [Kassapa Buddha, kalpa, Bhaddakappa (Auspicious Aeon)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kalpa Context triple: [Kassapa Buddha, kalpa, Bhaddakappa (Auspicious Aeon)]
-
A.
kapsam
Indicates that one entity includes, covers, or encompasses another within its scope or range.
-
B.
kāṇḍa
Indicates a part–whole relationship where something is a section, chapter, or subdivision of a larger structured whole.
-
C.
pakad
Indicates the act of catching, holding, or seizing someone or something, typically by grasping or capturing it.
-
D.
yugaCycle
chosen
Indicates a cyclical temporal relationship in which events, states, or entities are organized according to recurring ages or epochs within a repeating cosmic time cycle.
-
E.
yaksha
Indicates a relationship or action involving a yaksha, typically denoting interaction with, influence by, or association to this mythological being.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f7053f88190950d9cbc7f455ed2 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.