Triple
T12262005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddhist Lent |
E292246
|
entity |
| Predicate | mainPractices |
P1188
|
FINISHED |
| Object | meditation |
—
|
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: meditation | Statement: [Buddhist Lent, mainPractices, meditation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPractices Context triple: [Buddhist Lent, mainPractices, meditation]
-
A.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
B.
recommendedPracticeDefinition
Indicates that one entity defines or specifies the content or meaning of a recommended practice associated with another entity.
-
C.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
currentBestPractice
Indicates that something represents the most up-to-date and widely accepted recommended method or standard at the present time.
-
E.
hasImportantPractice
chosen
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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.