Triple
T3718609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | reasons for the commandments (ta'amei ha-mitzvot) |
E81587
|
entity |
| Predicate | includesDiscussionOf |
P33880
|
FINISHED |
| Object | chukkim |
—
|
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: chukkim | Statement: [reasons for the commandments (ta'amei ha-mitzvot), includesDiscussionOf, chukkim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDiscussionOf Context triple: [reasons for the commandments (ta'amei ha-mitzvot), includesDiscussionOf, chukkim]
-
A.
containsDiscussionOf
chosen
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
B.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca984844819087a2f6b20d2f19e7 |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.