Triple
T8693565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilderness wanderings (Sukkot) |
E206349
|
entity |
| Predicate | associatedWithCommandment |
P60020
|
FINISHED |
| Object | mitzvah of sukkah |
—
|
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: mitzvah of sukkah | Statement: [Wilderness wanderings (Sukkot), associatedWithCommandment, mitzvah of sukkah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCommandment Context triple: [Wilderness wanderings (Sukkot), associatedWithCommandment, mitzvah of sukkah]
-
A.
containsCommandment
chosen
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
B.
commandmentType
Indicates the specific category or kind of commandment that an instruction or directive belongs to.
-
C.
numberOfCommandments
Indicates the total count of commandments associated with a given subject.
-
D.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
E.
commandmentHebrewName
Indicates the Hebrew-language name assigned to a particular commandment.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5826bbb48190a212fb1bb06e05e6 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.