Triple
T10166214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maaser Sheni |
E235209
|
entity |
| Predicate | appliesInYears |
P92184
|
FINISHED |
| Object | first year of the Shemitah cycle |
—
|
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: first year of the Shemitah cycle | Statement: [Maaser Sheni, appliesInYears, first year of the Shemitah cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesInYears Context triple: [Maaser Sheni, appliesInYears, first year of the Shemitah cycle]
-
A.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
B.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
D.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
E.
type1Years
Indicates the number of years associated with being in or under a specified "type1" classification or status.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.