Triple
T19395251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaman |
E485171
|
entity |
| Predicate | hasFestivalObservance |
P38636
|
FINISHED |
| Object | Janmashtami celebrations |
—
|
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: Janmashtami celebrations | Statement: [Kaman, hasFestivalObservance, Janmashtami celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFestivalObservance Context triple: [Kaman, hasFestivalObservance, Janmashtami celebrations]
-
A.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
B.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
C.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
D.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
E.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b4875ac8190a9c184c075b5db16 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.