Triple
T14095695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bein haMetzarim |
E339247
|
entity |
| Predicate | marriageRestriction |
P112803
|
FINISHED |
| Object | customary avoidance of weddings |
—
|
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: customary avoidance of weddings | Statement: [Bein haMetzarim, marriageRestriction, customary avoidance of weddings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageRestriction Context triple: [Bein haMetzarim, marriageRestriction, customary avoidance of weddings]
-
A.
marriageTerritory
Indicates that a marriage is legally or socially recognized within a specific geographic or jurisdictional territory.
-
B.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
C.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
D.
marriageLegalStatus
Indicates the legal status of a marriage relationship between entities, such as whether it is valid, invalid, pending, or dissolved under applicable law.
-
E.
marriageClauseCondition
Indicates that a specific condition or set of conditions related to a marriage clause must be satisfied for the associated legal or contractual effect to apply.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.