Triple
T27494212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubosot |
E693978
|
entity |
| Predicate | legalStatusInSangha |
P21134
|
FINISHED |
| Object | consecrated ritual space |
—
|
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: consecrated ritual space | Statement: [Ubosot, legalStatusInSangha, consecrated ritual space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInSangha Context triple: [Ubosot, legalStatusInSangha, consecrated ritual space]
-
A.
statusInBuddhism
Indicates the recognized role, standing, or significance an entity holds within Buddhist doctrine, practice, or community.
-
B.
religiousAuthorityStatus
Indicates the role or level of recognized authority an entity holds within a religious or spiritual hierarchy.
-
C.
isOrdained
Indicates that an entity has been formally conferred religious or clerical authority through an official ordination process.
-
D.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
E.
sacredStatus
chosen
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 1:07 p.m.