Triple
T640748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adar I |
E16733
|
entity |
| Predicate | positionInLeapYear |
P16472
|
FINISHED |
| Object | 12th month |
—
|
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: 12th month | Statement: [Adar I, positionInLeapYear, 12th month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLeapYear Context triple: [Adar I, positionInLeapYear, 12th month]
-
A.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
B.
hasDayCountLeapYear
Indicates that the associated day count value applies specifically to a leap year.
-
C.
hasLeapMonth
Indicates that a given calendar year includes an extra (intercalary) month beyond the standard set of months.
-
D.
usesLeapYearException
Indicates that a rule, calculation, or process applies a special case or adjustment specifically for leap years.
-
E.
positionInHebrewCalendar
chosen
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f0189b08190a584b744f36fa761 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.