Triple
T4944361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solemnity |
E111009
|
entity |
| Predicate | hasProperLiturgyOfTheHours |
P60087
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Solemnity, hasProperLiturgyOfTheHours, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperLiturgyOfTheHours Context triple: [Solemnity, hasProperLiturgyOfTheHours, true]
-
A.
hasLiturgicalStructure
Indicates that something possesses an established form or order of worship, ritual, or liturgical arrangement.
-
B.
hasLiturgicalCelebration
Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
-
C.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
D.
hasLiturgicalContext
Indicates that something is associated with, used in, or relevant to a formal religious or liturgical setting or practice.
-
E.
hasSecondaryLiturgy
Indicates that an entity is associated with an additional, subordinate liturgical service or rite beyond its primary liturgy.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a8e5388190882831d7828441d3 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6fa2d2088190ae444d3d0e47d5d2 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 20, 2026, 1:31 p.m.