Triple
T23451133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pura Ulun Danu Batur |
E567782
|
entity |
| Predicate | hasRitualRole |
P76307
|
FINISHED |
| Object | regulating water distribution |
—
|
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: regulating water distribution | Statement: [Pura Ulun Danu Batur, hasRitualRole, regulating water distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualRole Context triple: [Pura Ulun Danu Batur, hasRitualRole, regulating water distribution]
-
A.
hasRitualRoleIn
chosen
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
B.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
-
D.
hasRitualCustodian
Indicates that one entity serves as the designated custodian or caretaker responsible for performing, preserving, or overseeing the rituals associated with another entity.
-
E.
hasRitualSystem
Indicates that an entity possesses or is associated with a structured set of rituals or ceremonial practices.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64d3e9c8190a2596b067c4f5061 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.