Triple
T37341231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Risshū |
E927042
|
entity |
| Predicate | monasticCodeType |
P41378
|
FINISHED |
| Object | fully ordained monastic precepts |
—
|
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: fully ordained monastic precepts | Statement: [Risshū, monasticCodeType, fully ordained monastic precepts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticCodeType Context triple: [Risshū, monasticCodeType, fully ordained monastic precepts]
-
A.
monasticCode
chosen
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
-
B.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
C.
monasticModel
Indicates a relationship where one entity serves as a pattern, example, or standard of monastic life or practice for another entity.
-
D.
religiousOrderCode
Indicates the specific religious order or denomination with which an entity is affiliated, represented by a standardized code.
-
E.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.