Triple
T31311368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epip |
E798470
|
entity |
| Predicate | typicalGregorianEndApproxLeapShift |
—
|
GENERATED |
| Object | August 7 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianEndApproxLeapShift Context triple: [Epip, typicalGregorianEndApproxLeapShift, August 7]
-
A.
leapYearGregorianDate
Indicates that a given date falls in a year that is a leap year according to the rules of the Gregorian calendar.
-
B.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
C.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
D.
leapMonthFrequencyApprox
Indicates how often leap months occur, expressed as an approximate frequency rather than an exact interval.
-
E.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
- F. None of above. chosen
Provenance (1 batch)
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.