Triple
T19083425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiki |
E467084
|
entity |
| Predicate | hasPracticeElement |
P36589
|
FINISHED |
| Object | hand positions on or above the body |
—
|
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: hand positions on or above the body | Statement: [Reiki, hasPracticeElement, hand positions on or above the body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPracticeElement Context triple: [Reiki, hasPracticeElement, hand positions on or above the body]
-
A.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
B.
hasPracticeFields
Indicates that an entity possesses or is associated with one or more designated fields or areas used for practice activities.
-
C.
isPracticedAt
Indicates that an activity, skill, or discipline is regularly performed or carried out at a particular location or context.
-
D.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
E.
practiceElement
chosen
Indicates that one entity is a component, step, or sub-activity within a broader practice or procedure involving 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.