Triple
T696514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aseret Yemei Teshuvah |
E13904
|
entity |
| Predicate | practiceIncludes |
P1393
|
FINISHED |
| Object | increased Torah study |
—
|
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: increased Torah study | Statement: [Aseret Yemei Teshuvah, practiceIncludes, increased Torah study]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practiceIncludes Context triple: [Aseret Yemei Teshuvah, practiceIncludes, increased Torah study]
-
A.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
B.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
C.
practicedLawIn
Indicates that a person engaged in the professional practice of law within a specified jurisdiction or location.
-
D.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.