Triple
T38049674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anapanasati Sutta |
E949717
|
entity |
| Predicate | secondTetradFocus |
P201092
|
FINISHED |
| Object | feelings |
—
|
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: feelings | Statement: [Anapanasati Sutta, secondTetradFocus, feelings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTetradFocus Context triple: [Anapanasati Sutta, secondTetradFocus, feelings]
-
A.
secondPartFocus
Indicates that the communicative or informational focus is placed on the second part or element in a two-part structure or relation.
-
B.
secondEditionFocus
Indicates that the relationship or content specifically pertains to the second edition version or focus of something, as opposed to other editions.
-
C.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
D.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
E.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
- 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_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69ffc70423f08190bd7c0625b21147a4 |
completed | May 9, 2026, 11:45 p.m. |
Created at: May 3, 2026, 4:20 p.m.