Triple
T23079103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahakaleshwar Temple, Ujjain |
E575417
|
entity |
| Predicate | BhasmaAartiTime |
P77079
|
FINISHED |
| Object | early morning |
—
|
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: early morning | Statement: [Mahakaleshwar Temple, Ujjain, BhasmaAartiTime, early morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BhasmaAartiTime Context triple: [Mahakaleshwar Temple, Ujjain, BhasmaAartiTime, early morning]
-
A.
hasAshramaAt
Indicates that an ashrama (hermitage or spiritual retreat) is located at or associated with a specific place.
-
B.
currentMahant
Indicates that the subject is the person who currently holds the position or role of Mahant (head or chief) of the referenced religious institution or community.
-
C.
performedYajnaFor
Indicates that one entity conducted or officiated a yajna (a Vedic ritual sacrifice) on behalf of or in honor of another entity.
-
D.
mainRitualTime
chosen
Indicates the time at which the primary or central ritual is performed.
-
E.
isKuldeviFor
Indicates a relationship where a particular goddess is revered as the ancestral or family deity (kuldevi) for a specific person, family, or lineage.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c6572d88190afab0dfa960a85dd |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:56 p.m.