Triple
T29197918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite Divine Liturgy |
E740179
|
entity |
| Predicate | alsoCelebratedOn |
P84580
|
FINISHED |
| Object | holy days of obligation |
—
|
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: holy days of obligation | Statement: [Maronite Divine Liturgy, alsoCelebratedOn, holy days of obligation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCelebratedOn Context triple: [Maronite Divine Liturgy, alsoCelebratedOn, holy days of obligation]
-
A.
isCelebrated
Indicates that a person, event, or occasion is honored, commemorated, or festively observed by others.
-
B.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
C.
isCelebratedAs
Indicates that an entity is recognized, honored, or regarded in a particular role, status, or capacity.
-
D.
celebratedDay
chosen
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
E.
mainlyCelebratedBy
Indicates that an event, tradition, or occasion is primarily observed or celebrated by a particular group or category of people.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c2f7a481908481c41c06579b39 |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:05 p.m.