Triple
T25421967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saka era |
E637008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu calendar era |
C42203
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hindu calendar era Context triple: [Saka era, instanceOf, Hindu calendar era]
-
A.
Hindu calendrical era
chosen
A Hindu calendrical era is a system of reckoning time that begins from a specific epochal event or legendary date and is used to number years in traditional Hindu calendars.
-
B.
period in the Hindu calendar
A period in the Hindu calendar is a defined span of time, such as a tithi, paksha, month, or season, used to organize religious observances, festivals, and astrological calculations.
-
C.
calendar era system
A calendar era system is a method of dating events by counting years from a specific starting point (epoch) defined by a cultural, religious, or historical reference.
-
D.
Sikh calendar
The Sikh calendar is a lunisolar timekeeping system, primarily the Nanakshahi calendar, used to determine Sikh religious festivals, historical commemorations, and the observance of important dates in Sikhism.
-
E.
Javanese calendrical system
The Javanese calendrical system is a syncretic timekeeping framework that combines elements of Hindu-Buddhist, Islamic, and indigenous Javanese traditions into a complex cycle of solar, lunar, and five-day market weeks used for ritual, agricultural, and social purposes.
- F. None of above.
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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:56 p.m.