Triple
T15684369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidovdan |
E380158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian religious holiday |
C8654
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Serbian religious holiday Context triple: [Vidovdan, instanceOf, Serbian religious holiday]
-
A.
event in Serbian history
A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
-
B.
Eastern Christian feast
chosen
An Eastern Christian feast is a liturgical celebration observed in the Eastern Christian traditions, commemorating events in the life of Christ, the Theotokos, or the saints according to their distinctive calendar and rites.
-
C.
organ of the Serbian Orthodox Church
An organ of the Serbian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or organizational functions within the Church’s hierarchical structure.
-
D.
Serbian Orthodox priest
A Serbian Orthodox priest is a Christian cleric ordained in the Serbian Orthodox Church who leads liturgical services, administers sacraments, offers spiritual guidance, and upholds the traditions and teachings of Eastern Orthodoxy within the Serbian cultural and religious context.
-
E.
Christian religious festival
A Christian religious festival is a recurring celebration within the Christian tradition that commemorates key events in the life of Jesus Christ, the saints, or central doctrines of the faith through worship, ritual, and communal observance.
- F. None of above.
Provenance (1 batch)
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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:43 a.m.