Triple
T4513048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu lunisolar calendar |
E102093
|
entity |
| Predicate | determinesFestival |
P57103
|
FINISHED |
| Object | Diwali |
—
|
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: Diwali | Statement: [Hindu lunisolar calendar, determinesFestival, Diwali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinesFestival Context triple: [Hindu lunisolar calendar, determinesFestival, Diwali]
-
A.
hasFestivalContext
Indicates that something is related to, occurs within, or is characterized by the setting, activities, or circumstances of a festival.
-
B.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
C.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
-
D.
operatesFestival
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
E.
hasFestivityType
Indicates that an event or celebration is classified as belonging to a particular type of festivity.
- F. None of above. chosen
Provenance (4 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.