Triple
T38018211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satipatthana Sutta |
E948551
|
entity |
| Predicate | PaliTermForBodySection |
P57111
|
FINISHED |
| Object | kayanupassana |
—
|
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: kayanupassana | Statement: [Satipatthana Sutta, PaliTermForBodySection, kayanupassana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaliTermForBodySection Context triple: [Satipatthana Sutta, PaliTermForBodySection, kayanupassana]
-
A.
inBuddhistCanon
Indicates that something is included within, or recognized as part of, the Buddhist canonical scriptures.
-
B.
hasPaliName
chosen
Indicates that an entity is associated with a name expressed in the Pali language.
-
C.
hasBuddhistTerm
Indicates that one entity includes, references, or is associated with a term originating from or used within Buddhism.
-
D.
translatedSection
Indicates that one text section is a translation of another corresponding section in a different language or version.
-
E.
abhidharmaText
Indicates a relationship where a text is classified as or associated with Abhidharma literature within the Buddhist doctrinal corpus.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.