Triple
T11826685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Refuges |
E281275
|
entity |
| Predicate | PaliFormula |
P36541
|
FINISHED |
| Object | Buddhaṃ saraṇaṃ gacchāmi |
—
|
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: Buddhaṃ saraṇaṃ gacchāmi | Statement: [Three Refuges, PaliFormula, Buddhaṃ saraṇaṃ gacchāmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaliFormula Context triple: [Three Refuges, PaliFormula, Buddhaṃ saraṇaṃ gacchāmi]
-
A.
hasPaliName
Indicates that an entity is associated with a name expressed in the Pali language.
-
B.
recitesFormula
Indicates that one entity verbally or mentally repeats a specific formula, such as a set phrase, equation, or ritual wording, typically from memory.
-
C.
centralFormulaMeaning
Indicates that one formula or expression represents the primary or core meaning within a larger logical, mathematical, or semantic structure.
-
D.
hasDevotionalFormula
chosen
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
-
E.
numberOfSutras
Indicates the quantity or count of sutras associated with a given 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5ec3a148190bb184ba0d481b16a |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.