Triple
T31311326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmouti |
E798469
|
entity |
| Predicate | associatedWithLiturgicalReadings |
P21314
|
FINISHED |
| Object | Coptic lectionary |
E1947146
|
NE 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: Coptic lectionary | Statement: [Parmouti, associatedWithLiturgicalReadings, Coptic lectionary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLiturgicalReadings Context triple: [Parmouti, associatedWithLiturgicalReadings, Coptic lectionary]
-
A.
hasLiturgicalReading
Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
-
B.
pairedWithInLiturgy
Indicates that two entities are customarily used or referenced together within a liturgical context or ceremony.
-
C.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
D.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
E.
liturgicalAssociation
chosen
Indicates a relationship in which one entity is connected to another through shared or relevant liturgical use, function, or context.
- F. None of above.
Provenance (4 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e41f8408190a5f3b295ef0fe93a |
completed | June 11, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.