Triple
T30750006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassapa Buddha |
E782930
|
entity |
| Predicate | roleInEra |
P117687
|
FINISHED |
| Object | one of the past Buddhas preceding Gautama Buddha |
—
|
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: one of the past Buddhas preceding Gautama Buddha | Statement: [Kassapa Buddha, roleInEra, one of the past Buddhas preceding Gautama Buddha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEra Context triple: [Kassapa Buddha, roleInEra, one of the past Buddhas preceding Gautama Buddha]
-
A.
roleInHistoryOf
Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
-
B.
roleInFusionEra
Indicates that an entity holds or held a specific role, function, or position during the Fusion Era.
-
C.
livedInEra
chosen
Indicates that an entity existed or was active during a particular historical era or time period.
-
D.
roleInHumanHistory
Indicates the function, influence, or significance that an entity has had within the course of human history.
-
E.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
- 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_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 29, 2026, 8:38 p.m.