Triple
T6517955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic lunar calendar |
E148310
|
entity |
| Predicate | doesNotUseLeapMonths |
P71362
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Islamic lunar calendar, doesNotUseLeapMonths, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotUseLeapMonths Context triple: [Islamic lunar calendar, doesNotUseLeapMonths, true]
-
A.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
B.
hasLeapMonth
Indicates that a given calendar year includes an extra (intercalary) month beyond the standard set of months.
-
C.
occursAfterLeapMonthInLeapYears
Indicates that the referenced event or time period takes place after the leap month specifically in years that are designated as leap years.
-
D.
leapMonthRule
Indicates the rule or condition that determines when a leap month is inserted in a given calendar system.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.