Triple
T33054242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shemitah |
E845806
|
entity |
| Predicate | debtReleaseCalled |
P175753
|
FINISHED |
| Object | Shemittat Kesafim |
—
|
NE NERFINISHED |
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: Shemittat Kesafim | Statement: [Shemitah, debtReleaseCalled, Shemittat Kesafim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debtReleaseCalled Context triple: [Shemitah, debtReleaseCalled, Shemittat Kesafim]
-
A.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
B.
eventualRelease
Indicates that one entity will be released or set free at some point in the future, though the exact time may be unknown or unspecified.
-
C.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
releasesOnReturn
Indicates that an entity is released, freed, or made available again when another entity is returned or comes back.
-
E.
isReleasedAt
Indicates that an entity (such as a product, media item, or version) becomes publicly available or officially launched at a specific time or date.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.