Triple
T10113430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badíʻ calendar |
E218296
|
entity |
| Predicate | newYearCoincidesWith |
P92267
|
FINISHED |
| Object | vernal equinox |
—
|
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: vernal equinox | Statement: [Badíʻ calendar, newYearCoincidesWith, vernal equinox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newYearCoincidesWith Context triple: [Badíʻ calendar, newYearCoincidesWith, vernal equinox]
-
A.
newYearOccursIn
Indicates that the celebration or observance of New Year takes place within a specified temporal or calendrical context (such as a particular month, season, or year).
-
B.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
C.
newYearDateGregorian
Indicates the specific calendar date on which New Year’s Day occurs according to the Gregorian calendar.
-
D.
newYearObservedIn
Indicates that a particular New Year celebration or observance takes place in or is recognized within a specified location or region.
-
E.
newYearName
Indicates that an entity has a specific name or designation used for or during the New Year.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:04 p.m.