Triple
T23584731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vighneshvara |
E582309
|
entity |
| Predicate | worshippedAtTime |
P59364
|
FINISHED |
| Object | start of rituals |
—
|
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: start of rituals | Statement: [Vighneshvara, worshippedAtTime, start of rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshippedAtTime Context triple: [Vighneshvara, worshippedAtTime, start of rituals]
-
A.
worshippedDuring
chosen
Indicates that a religious figure, deity, or sacred object is the target of worship specifically during a given time period, event, or occasion.
-
B.
timePeriodOfWorship
Indicates the specific time period during which the worship activity takes place or is observed.
-
C.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
D.
worshippedThrough
Indicates that one entity is venerated, honored, or worshipped by means of, or via the medium of, another entity (such as a ritual, object, place, or intermediary).
-
E.
worshipPeriod
Indicates the time span or specific period during which an act of worship or religious devotion takes place.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02f68288190b348c7558a6a24e1 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.