Triple
T22875054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathismata |
E567299
|
entity |
| Predicate | liturgicalBookLocation |
P74946
|
FINISHED |
| Object | found in liturgical Psalter |
—
|
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: found in liturgical Psalter | Statement: [Kathismata, liturgicalBookLocation, found in liturgical Psalter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalBookLocation Context triple: [Kathismata, liturgicalBookLocation, found in liturgical Psalter]
-
A.
hasLiturgicalBook
Indicates that one entity possesses, uses, or is associated with a specific liturgical book in a religious or worship context.
-
B.
liturgicalTextsFoundIn
chosen
Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
-
C.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
D.
liturgicalCenter
Indicates that a place functions as the primary site for conducting and organizing liturgical or religious worship activities for a community.
-
E.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f57a1ec8190b8c6a0080d97a2a2 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.