Triple
T20843425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Completorium |
E513156
|
entity |
| Predicate | hasLiturgicalHourOrderPosition |
P142058
|
FINISHED |
| Object | last |
—
|
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: last | Statement: [Completorium, hasLiturgicalHourOrderPosition, last]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalHourOrderPosition Context triple: [Completorium, hasLiturgicalHourOrderPosition, last]
-
A.
hasProperLiturgyOfTheHours
Indicates that an entity follows or possesses the officially prescribed form of the Liturgy of the Hours.
-
B.
hasLiturgicalPosture
Indicates that an entity is associated with a specific bodily posture or position used in a liturgical or religious ritual context.
-
C.
hasLiturgicalPeriod
Indicates that something is associated with, occurs during, or is assigned to a specific liturgical period within a religious calendar.
-
D.
isPartOfLiturgicalUnit
Indicates that one element belongs to, and functions as a component within, a larger liturgical unit or structure.
-
E.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
- F. None of above. chosen
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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34cdf9881909f3340874bbee5bc |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.