Triple
T25283429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surapadman |
E633874
|
entity |
| Predicate | festivalCommemoratedIn |
P38636
|
FINISHED |
| Object | Skanda Sashti |
—
|
NE NERFINISHED |
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: Skanda Sashti | Statement: [Surapadman, festivalCommemoratedIn, Skanda Sashti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalCommemoratedIn Context triple: [Surapadman, festivalCommemoratedIn, Skanda Sashti]
-
A.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
B.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
C.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
D.
festivalHeldIn
Indicates that a festival takes place or is hosted at a specific location or venue.
-
E.
isCelebratedWith
Indicates that an event, occasion, or person is marked or honored using a particular method, activity, or accompanying element (e.g., a party, ritual, or object).
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0718908190a2ebc862db79e2ea |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:19 p.m.