Triple
T158770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mezuzah |
E3233
|
entity |
| Predicate | isNotRequiredFor |
P6844
|
FINISHED |
| Object | temporary booths |
—
|
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: temporary booths | Statement: [mezuzah, isNotRequiredFor, temporary booths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotRequiredFor Context triple: [mezuzah, isNotRequiredFor, temporary booths]
-
A.
doesNotAutomaticallyProvide
Indicates that something is not supplied or made available by default and requires an explicit action or request to be provided.
-
B.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
doesNotParticipateIn
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
-
E.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.