Triple
T29856289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan lunar calendar |
E758196
|
entity |
| Predicate | leapMonthFrequency |
P57101
|
FINISHED |
| Object | every 2 or 3 years |
—
|
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 2 or 3 years | Statement: [Tibetan lunar calendar, leapMonthFrequency, every 2 or 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leapMonthFrequency Context triple: [Tibetan lunar calendar, leapMonthFrequency, every 2 or 3 years]
-
A.
leapMonthFrequencyApprox
chosen
Indicates how often leap months occur, expressed as an approximate frequency rather than an exact interval.
-
B.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
C.
hasLeapYearFrequency
Indicates how often leap years occur within a given temporal pattern or calendar system.
-
D.
leapMonthRule
Indicates the rule or condition that determines when a leap month is inserted in a given calendar system.
-
E.
occursAfterLeapMonthInLeapYears
Indicates that the referenced event or time period takes place after the leap month specifically in years that are designated as leap years.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6764cbaac81908d3eea5ae5833153 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:46 p.m.