Triple
T25961140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaishakha |
E645539
|
entity |
| Predicate | KrishnaPakshaEndsOn |
P159605
|
FINISHED |
| Object | Vaishakha Amavasya |
—
|
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: Vaishakha Amavasya | Statement: [Vaishakha, KrishnaPakshaEndsOn, Vaishakha Amavasya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KrishnaPakshaEndsOn Context triple: [Vaishakha, KrishnaPakshaEndsOn, Vaishakha Amavasya]
-
A.
hasNumberOfTithis
Indicates the relationship that specifies how many tithis (lunar days) are associated with a given entity or period.
-
B.
hasEkadashi
Indicates a relationship where an entity is associated with, observes, or is characterized by the occurrence of Ekadashi (the eleventh day of the lunar fortnight).
-
C.
day1OfBoishakhInIndia
Indicates the relationship where a given date is the first day of the month of Boishakh as observed in India.
-
D.
hasPositionInPaksha
Indicates that an entity holds a specific role or position within a particular Paksha (faction, side, or group).
-
E.
tithiRange
Indicates a relationship where something occurs, applies, or is valid within a specified range of lunar days (tithis) in a lunar calendar.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c60fe0819092ad09d1c5b0c100 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:47 a.m.