Triple
T26224055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hera Panchami |
E655840
|
entity |
| Predicate | occursRelativeToEvent |
P131136
|
FINISHED |
| Object | fourth day after Ratha Yatra begins |
—
|
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: fourth day after Ratha Yatra begins | Statement: [Hera Panchami, occursRelativeToEvent, fourth day after Ratha Yatra begins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursRelativeToEvent Context triple: [Hera Panchami, occursRelativeToEvent, fourth day after Ratha Yatra begins]
-
A.
relativeToEvent
chosen
Indicates that something is defined, measured, or interpreted in relation to a specific event as its reference point.
-
B.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
C.
posedAtEvent
Indicates that an entity assumed a particular pose or posture during a specified event.
-
D.
occursInRelationTo
Indicates that an event, process, or state takes place in the context of, or with reference to, another specified entity or relationship.
-
E.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:57 p.m.