Triple
T22701471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Klungkung |
E561333
|
entity |
| Predicate | religiousCeremonies |
P21643
|
FINISHED |
| Object | Balinese royal rituals |
—
|
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: Balinese royal rituals | Statement: [Kingdom of Klungkung, religiousCeremonies, Balinese royal rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCeremonies Context triple: [Kingdom of Klungkung, religiousCeremonies, Balinese royal rituals]
-
A.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
B.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
C.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
D.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
E.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cb2f548190bfc6f050be7c795a |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:15 p.m.