Triple
T1134647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symeon the New Theologian |
E23110
|
entity |
| Predicate | monasticRole |
P9873
|
FINISHED |
| Object | abbot |
—
|
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: abbot | Statement: [Symeon the New Theologian, monasticRole, abbot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticRole Context triple: [Symeon the New Theologian, monasticRole, abbot]
-
A.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
B.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
C.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
D.
dominantMonasticOrders
Indicates that certain monastic orders hold primary influence, prevalence, or control within a given religious or geographic context.
-
E.
theologicalRole
chosen
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.