Triple
T29585434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amshir |
E753705
|
entity |
| Predicate | hasCopticLiturgicalUse |
P9871
|
FINISHED |
| Object | determining readings and fasts |
—
|
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: determining readings and fasts | Statement: [Amshir, hasCopticLiturgicalUse, determining readings and fasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCopticLiturgicalUse Context triple: [Amshir, hasCopticLiturgicalUse, determining readings and fasts]
-
A.
hasLiturgicalMention
Indicates that one entity is referenced or mentioned within the liturgical texts, practices, or rites associated with another entity.
-
B.
usedInLiturgy
chosen
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
C.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
-
D.
hasLiturgicalMeaning
Indicates that something possesses a specific significance or function within a religious or liturgical context.
-
E.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: April 28, 2026, 6:10 p.m.