Triple
T35483838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akshaya Navami |
E1025536
|
entity |
| Predicate | lunarMonth |
P75844
|
FINISHED |
| Object | Kartika |
—
|
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: Kartika | Statement: [Akshaya Navami, lunarMonth, Kartika]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarMonth Context triple: [Akshaya Navami, lunarMonth, Kartika]
-
A.
lunarCalendar
Indicates that the referenced system, event, or date is defined, measured, or scheduled according to a calendar based on the phases or cycles of the Moon.
-
B.
dayOfLunarFortnight
Indicates the specific numbered day within a given lunar fortnight (half of a lunar month) on which an event or relation occurs.
-
C.
lunarQuadrant
Indicates a relationship where an entity is located within, or associated with, a specific quadrant or sector of the Moon’s surface.
-
D.
festivalMonthLunarCalendar
chosen
Indicates that a festival occurs in a specified month according to the lunar calendar.
-
E.
hasLunarFortnight
Indicates that an entity experiences or is associated with a recurring time period corresponding to a lunar fortnight (approximately half a lunar month).
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.