Triple
T29197928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite Divine Liturgy |
E740179
|
entity |
| Predicate | usesLiturgicalColors |
P171476
|
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: [Maronite Divine Liturgy, usesLiturgicalColors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLiturgicalColors Context triple: [Maronite Divine Liturgy, usesLiturgicalColors, yes]
-
A.
hasLiturgicalColor
Indicates that something is associated with a specific liturgical color used in religious rites or ceremonies.
-
B.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
C.
excludesLiturgicalColor
Indicates that a particular liturgical color is not permitted or is intentionally omitted in a given liturgical context, usage, or celebration.
-
D.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
E.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 12:05 p.m.