Triple
T1970822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dionysiou Monastery |
E42794
|
entity |
| Predicate | monasticTypikon |
P12141
|
FINISHED |
| Object | cenobitic |
—
|
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: cenobitic | Statement: [Dionysiou Monastery, monasticTypikon, cenobitic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticTypikon Context triple: [Dionysiou Monastery, monasticTypikon, cenobitic]
-
A.
monasticTradition
chosen
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
B.
monasticRepublic
Indicates a relationship where a territory or community is governed as a self-administered monastic state, combining religious monastic rule with a form of republican self-governance.
-
C.
liturgicalSequence
Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
-
D.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3d2836c8190a35cb6d8e2dd4bdf |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.