Zhipu Qingyan Bazi: Model Continuation and Calendar Limits

智谱清言算八字 refers to the practice of entering a birth date into 智谱清言, a general-purpose conversational model, and asking it to calculate a bazi chart. Bazi calculation depends on converting the stated birth date into the sexagenary pillars for the year, month, day, and hour. For a general language model, this conversion is not primarily a lookup in a calendrical table; it is a form of text continuation based on token generation. The model tends to produce plausible-looking 干支 sequences, but the output should be understood as generated prose rather than the result of a dedicated calendrical engine.

用一个闰月出生的生日去测,

A useful test is to give the model a lunar birth date that falls in a leap month and observe whether it first asks for the Gregorian date or immediately begins laying out the chart. The leap-month case is revealing because a lunar date cannot be mapped to a Gregorian date without first resolving the calendar system and the leap-month designation. If the model does not ask for clarification, it is likely treating the lunar numbers as though they were Gregorian numbers.

In this test, the user might write a birth date such as 闰四月初八 and ask for the bazi. The expected response from a careful tool would begin by establishing whether the supplied date is lunar or Gregorian. If the tool instead proceeds directly to a chart, that immediate response is a sign that the calendrical distinction has not been handled.

农历闰月是怎么回事,

The Chinese lunar calendar inserts leap months to keep the lunar year aligned with the tropical year. Because a lunar year of twelve lunar months is shorter than a tropical year, the calendar periodically adds an extra month. The leap month is given the same name as the preceding month and is written with the prefix 闰, producing forms such as 闰四月 or 闰六月.

A leap month does not introduce a new month name. It repeats the previous month’s name, and this repetition is what creates ambiguity when someone gives only the month and day. The same designation, such as 四月初八, may occur twice in a single lunar year if that year contains a leap fourth month.

月柱按节气划分，不按农历月,

In bazi calculation, the month pillar is divided according to the solar terms, not according to lunar month boundaries. The month pillar changes at the 节 points, such as 立春，惊蛰，清明, and the other major solar terms. These points are based on the sun’s position and do not coincide with the first day of a lunar month.

For this reason, the presence of a leap month does not by itself change how the month pillar is derived. The month pillar is tied to the solar-term cycle, so the extra lunar month is not a separate branch in the month-pillar sequence. The calculation still follows the twelve solar-term months.

The distinction matters when a user supplies a lunar date. A lunar month may begin in the middle of a solar-term month, and a leap month may span parts of two solar-term months. Without converting the lunar date to a Gregorian date and then locating the correct solar-term interval, the month pillar can be assigned incorrectly.

闰月输入最容易带出的一种错,

The most common error in leap-month input occurs when a tool treats the lunar numbers as Gregorian numbers. If a user enters 闰四月初八 and the system ignores the calendar marker, it may read the input as April 8 of a Gregorian year. In that case the year, month, and day pillars can all be affected.

When the date is treated as Gregorian, the year pillar may be taken from the wrong year boundary, the month pillar may fall in the wrong solar-term interval, and the day pillar will refer to a different day entirely. A leap-month date such as 闰四月初八 does not correspond to April 8 in any direct way. The Gregorian date must be found by converting the lunar calendar position for that specific year.

The error is not limited to the month pillar. Because the Gregorian day number is reused as if it were a lunar day number, the sexagenary day count shifts. The resulting chart may look internally consistent, but it will not match the chart produced from the correct Gregorian date.

提交之前把历法写清楚的一句话,

Before submitting a birth date to any bazi tool, it is useful to state the calendar system in one sentence. A simple formulation such as 以下是公历日期 or 以下是农历日期，请先换算 removes the ambiguity that leads to misread dates.

For a model like 智谱清言, the instruction serves as a prompt constraint. It tells the model whether the numbers should be used as they are or first converted. This is especially important when the date falls in a leap month, because the same lunar month and day may correspond to two different Gregorian dates in the same year. Stating the calendar system before giving the date tends to reduce the chance that the model will silently treat lunar input as Gregorian.

The leap-month case also shows why the calendar statement alone is not always enough. If the user writes 四月初八 without specifying whether it is a leap month, the date may be ambiguous even after the calendar system is stated. In a year with a leap fourth month, the label 四月初八 can refer to the regular fourth month or to 闰四月. The safe practice is to include the leap-month marker when it applies and to state the calendar system in the same submission.

A well-formed request might therefore read: 以下是农历日期，闰四月初八，请先换算为公历再排八字. This gives the model the calendar system, the leap-month designation, and the instruction to convert before calculating. Without this level of clarity, the tool may begin laying out a chart from the first numbers it recognizes.

The test with a leap-month birthday is best understood as a diagnostic of how a conversational model handles calendrical input. It does not measure whether the model knows bazi theory in any broad sense. It measures whether the model recognizes that a lunar leap-month date is not directly usable as a Gregorian date. When the model asks for clarification, it is at least treating the input as a date that requires conversion. When it proceeds directly, it is likely treating the lunar digits as Gregorian digits, and the year, month, and day pillars may all shift as a result.

For users of general-purpose dialogue systems, the practical conclusion is not that such models are unusable for bazi calculation, but that the input needs to be disambiguated before the model begins. The calendar system should be stated explicitly, the leap-month marker should be included when relevant, and the model should be asked to convert the date before laying out the chart. Even then, the output remains generated text rather than a checked calendrical computation, and it should be read with that limitation in mind.