Triple
T2927262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraljevo (Žiča) |
E78874
|
entity |
| Predicate | primaryLiturgicalLanguageToday |
P3115
|
FINISHED |
| Object | Serbian |
—
|
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: Serbian | Statement: [Kraljevo (Žiča), primaryLiturgicalLanguageToday, Serbian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLiturgicalLanguageToday Context triple: [Kraljevo (Žiča), primaryLiturgicalLanguageToday, Serbian]
-
A.
usesPrimaryLiturgicalLanguageHistorically
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
-
B.
languageOfWorship
chosen
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
D.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
E.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.