Triple
T511249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purim |
E10611
|
entity |
| Predicate | workRestrictions |
P10734
|
FINISHED |
| Object | no full work prohibition in most communities |
—
|
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: no full work prohibition in most communities | Statement: [Purim, workRestrictions, no full work prohibition in most communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workRestrictions Context triple: [Purim, workRestrictions, no full work prohibition in most communities]
-
A.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
-
B.
notableRestriction
chosen
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
C.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
D.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
E.
formerLegalRestriction
Indicates that a legal restriction once applied to an entity or relationship but is no longer in effect.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f165b91c81908c2d2ba15c64b956 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edff001c81909182a7e26c6dc51b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.