Triple
T38049655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anapanasati Sutta |
E949717
|
entity |
| Predicate | hasTitleInPali |
P46856
|
FINISHED |
| Object | Ānāpānassati Sutta |
—
|
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: Ānāpānassati Sutta | Statement: [Anapanasati Sutta, hasTitleInPali, Ānāpānassati Sutta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInPali Context triple: [Anapanasati Sutta, hasTitleInPali, Ānāpānassati Sutta]
-
A.
titleInSanskritScript
Indicates that the title of an entity is expressed using the Sanskrit writing system.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleInRevisedRomanization
Indicates that an entity has a specific title expressed using the Revised Romanization system for Korean.
-
D.
hasTitleInTransliteration
chosen
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
-
E.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:20 p.m.