Triple
T34816133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pausha |
E1003640
|
entity |
| Predicate | containsLunarPhase |
P202503
|
FINISHED |
| Object | Purnima |
—
|
NE NERFINISHED |
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: Purnima | Statement: [Pausha, containsLunarPhase, Purnima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLunarPhase Context triple: [Pausha, containsLunarPhase, Purnima]
-
A.
hasLunarPhaseStart
Indicates that an entity (such as a lunar phase event) has a specific starting time or point at which that lunar phase begins.
-
B.
hasLunarFortnight
Indicates that an entity experiences or is associated with a recurring time period corresponding to a lunar fortnight (approximately half a lunar month).
-
C.
startsOnLunarDate
Indicates that an event or interval begins on a specific date defined according to a lunar calendar system.
-
D.
astronomicalPhase
Indicates the specific stage or phase an astronomical object (such as a planet or moon) is in within its cyclical progression as observed over time.
-
E.
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.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
| PDg | Predicate description generation | batch_6a008b8870b481909c1a2707a7b06d49 |
completed | May 10, 2026, 1:43 p.m. |
Created at: May 3, 2026, 3:59 p.m.