Triple
T2722394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asalha Puja |
E60110
|
entity |
| Predicate | observedInCalendar |
P1818
|
FINISHED |
| Object | traditional lunar calendar |
—
|
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: traditional lunar calendar | Statement: [Asalha Puja, observedInCalendar, traditional lunar calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInCalendar Context triple: [Asalha Puja, observedInCalendar, traditional lunar calendar]
-
A.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
D.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
E.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab2f36c8190aa0b452e57525fe0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.