Triple
T337945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shavuot |
E6768
|
entity |
| Predicate | workProhibition |
P8268
|
FINISHED |
| Object | Melacha forbidden like on other festivals |
—
|
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: Melacha forbidden like on other festivals | Statement: [Shavuot, workProhibition, Melacha forbidden like on other festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workProhibition Context triple: [Shavuot, workProhibition, Melacha forbidden like on other festivals]
-
A.
workProhibited
chosen
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
D.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
E.
workBecame
Indicates that one work was transformed, adapted, or evolved into another work over time.
- F. None of above.
Provenance (3 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae23b0c819081f8bf9ac26685ab |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.