Triple
T3816022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Week |
E84255
|
entity |
| Predicate | hasLiturgicalCharacter |
P13038
|
FINISHED |
| Object | penitential |
—
|
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: penitential | Statement: [Great Week, hasLiturgicalCharacter, penitential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalCharacter Context triple: [Great Week, hasLiturgicalCharacter, penitential]
-
A.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
B.
hasLiturgicalStructure
Indicates that something possesses an established form or order of worship, ritual, or liturgical arrangement.
-
C.
hasLiturgicalLife
Indicates that an entity participates in or maintains practices, rituals, and rhythms associated with liturgical worship.
-
D.
liturgicalCharacter
chosen
Indicates the specific role, function, or significance that something holds within a liturgical or worship context.
-
E.
hasPrimaryLiturgicalForm
Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.