Triple
T12784259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian Missal |
E305582
|
entity |
| Predicate | hasLiturgicalSeasonStructure |
P27467
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ethiopian Missal, hasLiturgicalSeasonStructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalSeasonStructure Context triple: [Ethiopian Missal, hasLiturgicalSeasonStructure, yes]
-
A.
hasLiturgicalStructure
chosen
Indicates that something possesses an established form or order of worship, ritual, or liturgical arrangement.
-
B.
hasLiturgicalPeriod
Indicates that something is associated with, occurs during, or is assigned to a specific liturgical period within a religious calendar.
-
C.
hasLiturgicalCycle
Indicates that one entity follows, observes, or is structured according to a particular liturgical cycle associated with another entity.
-
D.
liturgicalSeasonRelation
Indicates a relationship between entities based on their association with, occurrence in, or relevance to a particular liturgical season.
-
E.
hasLiturgicalContext
Indicates that something is associated with, used in, or relevant to a formal religious or liturgical setting or practice.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5cb3c08190b8e1e22de8b96e17 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.