Triple
T21136895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarvastivada Buddhism |
E520836
|
entity |
| Predicate | abhidharmaPreservedIn |
P142998
|
FINISHED |
| Object | Chinese canon |
—
|
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: Chinese canon | Statement: [Sarvastivada Buddhism, abhidharmaPreservedIn, Chinese canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abhidharmaPreservedIn Context triple: [Sarvastivada Buddhism, abhidharmaPreservedIn, Chinese canon]
-
A.
BuddhistTradition
Indicates that an entity follows, embodies, or is associated with Buddhist religious, philosophical, or cultural traditions.
-
B.
associatedSampradaya
Indicates a relationship where one entity is linked or connected to a particular sampradaya (spiritual or religious tradition/lineage) with which it is affiliated or identified.
-
C.
numberOfSutras
Indicates the quantity or count of sutras associated with a given entity.
-
D.
viewedAsByBuddhistTexts
Indicates how something is regarded, interpreted, or characterized specifically within Buddhist texts.
-
E.
monkWhoseTextsItHoused
Indicates that one entity is a monk whose texts or writings were stored, preserved, or housed by another entity.
- F. None of above. chosen
Provenance (4 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235b89188190a6209c0a1839ee03 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:57 p.m.