Triple
T26933311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National preceptor (in Korean Buddhist tradition) |
E678295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-appointed monastic position |
C6234
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: state-appointed monastic position Context triple: [National preceptor (in Korean Buddhist tradition), instanceOf, state-appointed monastic position]
-
A.
Byzantine ecclesiastical office
A Byzantine ecclesiastical office is a formal clerical position within the hierarchical structure of the Eastern Roman (Byzantine) Church, encompassing specific liturgical, administrative, and judicial duties tied to the empire’s religious and imperial governance.
-
B.
head of monastery
The head of a monastery is the senior religious leader responsible for the spiritual guidance, governance, discipline, and daily administration of the monastic community.
-
C.
office in a religious order
chosen
An office in a religious order is a formally designated role or position within the community that carries specific spiritual, administrative, or pastoral responsibilities in service of the order’s mission and governance.
-
D.
bishopric office
A bishopric office is an administrative and pastoral center where a bishop and their staff conduct the governance, coordination, and support of ecclesiastical activities within a diocese or similar church jurisdiction.
-
E.
religious role
A religious role is a socially recognized position within a faith tradition that carries specific spiritual, ritual, moral, or organizational responsibilities.
- F. None of above.
Provenance (1 batch)
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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:14 a.m.