Triple
T9831675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavadee |
E238999
|
entity |
| Predicate | preparatoryPractice |
P2534
|
FINISHED |
| Object | abstinence from meat |
—
|
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: abstinence from meat | Statement: [Cavadee, preparatoryPractice, abstinence from meat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparatoryPractice Context triple: [Cavadee, preparatoryPractice, abstinence from meat]
-
A.
initiationPractice
Indicates the act of beginning, launching, or formally starting a particular practice, process, or activity.
-
B.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
C.
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.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb335623c8190902de29795bce87d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.