Triple
T3110473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhath Puja |
E64936
|
entity |
| Predicate | observanceFeatures |
P12145
|
FINISHED |
| Object | strict ritual discipline |
—
|
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: strict ritual discipline | Statement: [Chhath Puja, observanceFeatures, strict ritual discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceFeatures Context triple: [Chhath Puja, observanceFeatures, strict ritual discipline]
-
A.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
B.
typicalObservances
chosen
Indicates the customary practices, rituals, or activities that are commonly carried out in association with something (such as an event, tradition, or occasion).
-
C.
observanceMayVaryByCountry
Indicates that the way something is observed, celebrated, or practiced can differ depending on the country.
-
D.
observancePattern
Indicates how an action, rule, or practice is regularly carried out or followed over time, such as its schedule, frequency, or customary pattern of observance.
-
E.
observanceMayVaryByYear
Indicates that the way an observance is recognized, scheduled, or practiced can differ from one year to another.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada437c5e08190af22f6fa11cf9252 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.