Triple
T29320070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velli |
E743491
|
entity |
| Predicate | observanceDayFor |
P84580
|
FINISHED |
| Object | goddess-related worship in some Tamil Hindu traditions |
—
|
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: goddess-related worship in some Tamil Hindu traditions | Statement: [Velli, observanceDayFor, goddess-related worship in some Tamil Hindu traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceDayFor Context triple: [Velli, observanceDayFor, goddess-related worship in some Tamil Hindu traditions]
-
A.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
B.
celebratedDay
chosen
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
C.
mayObserveHoliday
Indicates that an entity is permitted or allowed to observe or celebrate a particular holiday.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
holidayDateSystem
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:22 p.m.