Triple
T26920897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalpa Sutra |
E677642
|
entity |
| Predicate | primaryFestivalAssociation |
P41325
|
FINISHED |
| Object | Paryushana |
—
|
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: Paryushana | Statement: [Kalpa Sutra, primaryFestivalAssociation, Paryushana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFestivalAssociation Context triple: [Kalpa Sutra, primaryFestivalAssociation, Paryushana]
-
A.
associatedFestivalOrCustom
Indicates a festival or custom that is traditionally linked or related to the given entity.
-
B.
relatedFestivalType
Indicates that one festival is associated with another through a shared or corresponding festival type or category.
-
C.
mainFestival
chosen
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
D.
relationToMainFestival
Indicates how a given event, activity, or element is connected or related to the main festival.
-
E.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 27, 2026, 6:07 a.m.