Triple
T1032548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merkavah mysticism |
E22283
|
entity |
| Predicate | includesPractice |
P1393
|
FINISHED |
| Object | esoteric ritual practices |
—
|
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: esoteric ritual practices | Statement: [Merkavah mysticism, includesPractice, esoteric ritual practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPractice Context triple: [Merkavah mysticism, includesPractice, esoteric ritual practices]
-
A.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
-
B.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
C.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
D.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
hasImportantPractice
Indicates that an entity engages in or possesses a practice, activity, or procedure considered significant or essential within a given context.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.