Triple
T38049675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anapanasati Sutta |
E949717
|
entity |
| Predicate | thirdTetradFocus |
P194051
|
FINISHED |
| Object | mind |
—
|
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: mind | Statement: [Anapanasati Sutta, thirdTetradFocus, mind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdTetradFocus Context triple: [Anapanasati Sutta, thirdTetradFocus, mind]
-
A.
fourthTetradFocus
Indicates that the relationship or action pertains to the focus or theme associated with the fourth tetrad in a structured sequence of four-part groupings.
-
B.
thirdForce
Indicates that an additional, distinct force is acting on an entity beyond the primary two forces already considered.
-
C.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
-
D.
thirdFactor
Indicates that an entity serves as the third factor or element in a multi-factor relationship, typically complementing two other primary factors in a given context.
-
E.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:20 p.m.