Triple
T21085725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tawur Kesanga ritual |
E519481
|
entity |
| Predicate | centralRitualSite |
P90408
|
FINISHED |
| Object | major temples in Bali |
—
|
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: major temples in Bali | Statement: [Tawur Kesanga ritual, centralRitualSite, major temples in Bali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralRitualSite Context triple: [Tawur Kesanga ritual, centralRitualSite, major temples in Bali]
-
A.
ritualCentersOn
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
B.
mainLocationOfRituals
chosen
Indicates that a place serves as the primary setting where a group's rituals are regularly performed.
-
C.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
D.
centralDeitySymbol
Indicates that one entity serves as the primary or central symbolic representation of a deity for another entity.
-
E.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.