Triple
T4513035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu lunisolar calendar |
E102093
|
entity |
| Predicate | leapMonthFrequencyApprox |
P57101
|
FINISHED |
| Object | every 32.5 months |
—
|
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: every 32.5 months | Statement: [Hindu lunisolar calendar, leapMonthFrequencyApprox, every 32.5 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leapMonthFrequencyApprox Context triple: [Hindu lunisolar calendar, leapMonthFrequencyApprox, every 32.5 months]
-
A.
hasLeapYearFrequency
Indicates how often leap years occur within a given temporal pattern or calendar system.
-
B.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
C.
leapMonthRule
Indicates the rule or condition that determines when a leap month is inserted in a given calendar system.
-
D.
hasLeapMonth
Indicates that a given calendar year includes an extra (intercalary) month beyond the standard set of months.
-
E.
followsMonthInLeapYears
Indicates that one month directly succeeds another specifically in the context of leap years.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.