Triple
T34111596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Nanak Gurpurab |
E874851
|
entity |
| Predicate | typicalDateInNanakshahiCalendar |
P18044
|
FINISHED |
| Object | 1 Katak |
—
|
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: 1 Katak | Statement: [Guru Nanak Gurpurab, typicalDateInNanakshahiCalendar, 1 Katak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDateInNanakshahiCalendar Context triple: [Guru Nanak Gurpurab, typicalDateInNanakshahiCalendar, 1 Katak]
-
A.
typicalDates
chosen
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
B.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
C.
hasNumberOfTithis
Indicates the relationship that specifies how many tithis (lunar days) are associated with a given entity or period.
-
D.
dateVariesInGregorianCalendar
Indicates that the specific date associated with an event or entity is not fixed but changes from year to year when expressed in the Gregorian calendar.
-
E.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.