Triple
T14095696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bein haMetzarim |
E339247
|
entity |
| Predicate | groomingRestriction |
P112804
|
FINISHED |
| Object | customary avoidance of haircuts and shaving |
—
|
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 haircuts and shaving | Statement: [Bein haMetzarim, groomingRestriction, customary avoidance of haircuts and shaving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groomingRestriction Context triple: [Bein haMetzarim, groomingRestriction, customary avoidance of haircuts and shaving]
-
A.
groomingNeeds
Indicates the level, type, or frequency of grooming care required for an entity.
-
B.
hasGrooming
Indicates that one entity performs grooming behavior on, or receives grooming from, another entity.
-
C.
petPolicy
Indicates the rules or conditions governing whether and how pets are allowed in relation to a place, service, or arrangement.
-
D.
groomHouse
Indicates performing cleaning, organizing, or maintenance activities to keep a house neat and well-kept.
-
E.
cannotBeLeashed
Indicates that one entity is not allowed or not able to be restrained, controlled, or attached using a leash by 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_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.