Triple

T17939323
Position Surface form Disambiguated ID Type / Status
Subject Kartik Krishna Paksha E448546 entity
Predicate hasNumberOfTithis P129798 FINISHED
Object 15 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: 15 | Statement: [Kartik Krishna Paksha, hasNumberOfTithis, 15]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNumberOfTithis
Context triple: [Kartik Krishna Paksha, hasNumberOfTithis, 15]
  • 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. isLunisolar
    Indicates that something is based on or determined by both the cycles of the moon and the sun.
  • C. monthInHinduCalendar
    Indicates that a specified time or event falls within a particular month as defined by the Hindu calendar system.
  • D. hasNumberOfDaysIn13thMonth
    Indicates the specific count of days that occur in the thirteenth month of a given calendar or time system.
  • E. occursOnNakshatra
    Indicates that an event or phenomenon takes place during, or is associated with, a specific nakshatra (lunar mansion) in the traditional Indian astronomical/astrological system.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad9533688190bff773c183ed8505 completed April 19, 2026, 10:25 a.m.
PD Predicate disambiguation batch_69e3f8e713d481908b4a126258c18b63 completed April 18, 2026, 9:34 p.m.
PDg Predicate description generation batch_69e42d8d68288190a05dc5d7803cf823 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:21 a.m.