Triple
T36299689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashada month |
E893472
|
entity |
| Predicate | hasFullMoonDay |
P153061
|
FINISHED |
| Object | Guru 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: Guru Purnima | Statement: [Ashada month, hasFullMoonDay, Guru Purnima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullMoonDay Context triple: [Ashada month, hasFullMoonDay, Guru Purnima]
-
A.
hasLunarFortnight
Indicates that an entity experiences or is associated with a recurring time period corresponding to a lunar fortnight (approximately half a lunar month).
-
B.
hasApproximateStartAtNewMoon
Indicates that an event or period begins at a time that closely coincides with the occurrence of a new moon.
-
C.
isOnlyLargeMoonWith
Indicates that one moon is the sole large moon possessing a specified feature, property, or relationship among all moons in consideration.
-
D.
hasLunarPhaseStart
Indicates that an entity (such as a lunar phase event) has a specific starting time or point at which that lunar phase begins.
-
E.
dayOfLunarFortnight
chosen
Indicates the specific numbered day within a given lunar fortnight (half of a lunar month) on which an event or relation occurs.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.