Triple
T32627416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia (Buryatia, Kalmykia, Tuva) |
E834094
|
entity |
| Predicate | sharesFestivals |
P61046
|
FINISHED |
| Object | Buddhist New Year 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: Buddhist New Year celebrations | Statement: [Russia (Buryatia, Kalmykia, Tuva), sharesFestivals, Buddhist New Year celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesFestivals Context triple: [Russia (Buryatia, Kalmykia, Tuva), sharesFestivals, Buddhist New Year celebrations]
-
A.
shareCulturalFestivals
chosen
Indicates that two or more entities participate in or observe the same cultural festivals or celebrations.
-
B.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
C.
relatedFestivalDate
Indicates that there is a specific calendar date associated with a particular festival or celebration.
-
D.
festivalCalendar
Indicates that there is a scheduled festival or celebration associated with a particular time or date in a calendar.
-
E.
peerFestival
Indicates that two festivals are considered peers, sharing a comparable status, scale, or role within a given context.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 1, 2026, 1:06 a.m.