Triple
T2563136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakyamuni Buddha |
E57288
|
entity |
| Predicate | roleInBuddhism |
P2319
|
FINISHED |
| Object | founder of Buddhism |
—
|
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: founder of Buddhism | Statement: [Shakyamuni Buddha, roleInBuddhism, founder of Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBuddhism Context triple: [Shakyamuni Buddha, roleInBuddhism, founder of Buddhism]
-
A.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
C.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
D.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
E.
roleInTheology
chosen
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.