Triple
T17939452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tihar |
E448548
|
entity |
| Predicate | day5MainRitual |
P65752
|
FINISHED |
| Object | sister applies tika to brother |
—
|
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: sister applies tika to brother | Statement: [Tihar, day5MainRitual, sister applies tika to brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: day5MainRitual Context triple: [Tihar, day5MainRitual, sister applies tika to brother]
-
A.
mainRitualTime
Indicates the time at which the primary or central ritual is performed.
-
B.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
C.
day5Form
Indicates that an entity is associated with or presented in a specific "day 5" form, version, or configuration within a sequence or process.
-
D.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
E.
ritualActivities
chosen
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.