Triple
T34666903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Kinds |
E890280
|
entity |
| Predicate | requiresEtrogQuality |
P200169
|
FINISHED |
| Object | unblemished etrog |
—
|
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: unblemished etrog | Statement: [Four Kinds, requiresEtrogQuality, unblemished etrog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresEtrogQuality Context triple: [Four Kinds, requiresEtrogQuality, unblemished etrog]
-
A.
requiresZimunWhen
Indicates that a situation or context obligates the performance of Zimun (the formal invitation to communal grace after meals).
-
B.
hasEruv
Indicates that a place or area is enclosed within an eruv boundary, allowing certain activities (like carrying objects) that are otherwise restricted on the Jewish Sabbath.
-
C.
requiresMinyan
Indicates that the action or ritual can only be properly performed when a quorum (minyan) of participants is present.
-
D.
hasMashgiach
Indicates that an entity is supervised or overseen by a mashgiach (a kosher supervisor).
-
E.
hasFullSetOfPurimMitzvot
Indicates that an entity fulfills or possesses the complete set of religious commandments associated with the observance of Purim.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
| PDg | Predicate description generation | batch_69ff795c702c8190b00844407f2882af |
completed | May 9, 2026, 6:13 p.m. |
Created at: May 1, 2026, 2:05 a.m.