Triple
T6083012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balinese people |
E135567
|
entity |
| Predicate | traditionalReligionConcept |
P15107
|
FINISHED |
| Object | desa kala patra |
—
|
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: desa kala patra | Statement: [Balinese people, traditionalReligionConcept, desa kala patra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionConcept Context triple: [Balinese people, traditionalReligionConcept, desa kala patra]
-
A.
traditionalReligionName
Indicates that an entity has a name specifically associated with a traditional or indigenous religion.
-
B.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
C.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
D.
theologicalConcept
chosen
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05786233c81909010a6c2f7e7dfda |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.