Triple
T1106392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumbh Mela |
E25496
|
entity |
| Predicate | MahaKumbhFrequency |
P23194
|
FINISHED |
| Object | every 144 years at Prayagraj |
—
|
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: every 144 years at Prayagraj | Statement: [Kumbh Mela, MahaKumbhFrequency, every 144 years at Prayagraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MahaKumbhFrequency Context triple: [Kumbh Mela, MahaKumbhFrequency, every 144 years at Prayagraj]
-
A.
timePeriodOfWorship
Indicates the specific time period during which the worship activity takes place or is observed.
-
B.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
C.
pilgrimageTempleCount
Indicates the number of temples associated with or visited during a particular pilgrimage.
-
D.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
numberOfTirthankaras
Indicates the specific count of Tirthankaras associated with or attributed to an entity.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e339f88190afc027216e95d2f7 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:43 p.m.