Triple
T33054243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shemitah |
E845806
|
entity |
| Predicate | debtReleaseSource |
P67731
|
FINISHED |
| Object | Deuteronomy 15:1–3 |
—
|
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: Deuteronomy 15:1–3 | Statement: [Shemitah, debtReleaseSource, Deuteronomy 15:1–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debtReleaseSource Context triple: [Shemitah, debtReleaseSource, Deuteronomy 15:1–3]
-
A.
debtReleaseCalled
Indicates that an action has been initiated to cancel, forgive, or otherwise release an existing debt obligation.
-
B.
loanSource
chosen
Indicates that one entity is the origin or provider of a loan extended to another entity.
-
C.
debt
Indicates that one entity owes money or an obligation to another entity, typically to be repaid under agreed conditions.
-
D.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:24 a.m.