Triple
T38049672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anapanasati Sutta |
E949717
|
entity |
| Predicate | organizesPracticeInto |
P5709
|
FINISHED |
| Object | four tetrads |
—
|
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: four tetrads | Statement: [Anapanasati Sutta, organizesPracticeInto, four tetrads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesPracticeInto Context triple: [Anapanasati Sutta, organizesPracticeInto, four tetrads]
-
A.
collectivePractice
Indicates a shared or coordinated activity carried out by a group rather than by individuals acting separately.
-
B.
practiseAs
Indicates that an entity performs or is engaged in a particular profession, role, or occupation in an official or recognized capacity.
-
C.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
D.
settingOfPractice
Indicates the context or environment in which a particular practice, activity, or procedure is carried out.
-
E.
organizesInto
chosen
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
- 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_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:20 p.m.