Triple
T10877648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Species on Sukkot |
E256839
|
entity |
| Predicate | genderOfMitzvah |
P96200
|
FINISHED |
| Object | time-bound positive commandment |
—
|
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: time-bound positive commandment | Statement: [Four Species on Sukkot, genderOfMitzvah, time-bound positive commandment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderOfMitzvah Context triple: [Four Species on Sukkot, genderOfMitzvah, time-bound positive commandment]
-
A.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
B.
genderTarget
Indicates that an action, message, or effect is specifically directed toward entities of a particular gender.
-
C.
hasGenderInterpretation
Indicates that an entity is associated with a particular interpretation or understanding of gender.
-
D.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
-
E.
namedForGender
Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ad8cdc819093eafaf12fc23b15 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.