Triple
T35332448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama Ekadashi |
E1020357
|
entity |
| Predicate | observanceForm |
P126917
|
FINISHED |
| Object | temple worship of Vishnu |
—
|
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: temple worship of Vishnu | Statement: [Rama Ekadashi, observanceForm, temple worship of Vishnu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceForm Context triple: [Rama Ekadashi, observanceForm, temple worship of Vishnu]
-
A.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
B.
observanceRequires
Indicates that carrying out a particular observance or practice is contingent upon, or must be accompanied by, the fulfillment of a specified requirement or condition.
-
C.
observanceSetting
Indicates the context, environment, or circumstances in which an observance (such as a ritual, ceremony, or practice) takes place.
-
D.
observanceLinkedTo
chosen
Indicates a relationship where a particular observance (such as a ritual, ceremony, or commemorative act) is connected or associated with another entity, event, or concept.
-
E.
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.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.