Triple
T35358226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prabodhini Ekadashi |
E1021396
|
entity |
| Predicate | occursOnLunarDayNumber |
P153061
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Prabodhini Ekadashi, occursOnLunarDayNumber, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursOnLunarDayNumber Context triple: [Prabodhini Ekadashi, occursOnLunarDayNumber, 11]
-
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
chosen
Indicates the specific numbered day within a given lunar fortnight (half of a lunar month) on which an event or relation occurs.
-
C.
hasNumberOfTithis
Indicates the relationship that specifies how many tithis (lunar days) are associated with a given entity or period.
-
D.
bornOnLunarTithi
Indicates that one entity was born on the specific lunar tithi (lunar day) represented by the other entity.
-
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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.