Triple
T37427889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Approaching Christmas |
E930043
|
entity |
| Predicate | focusesOnLiturgicalSeason |
P25898
|
FINISHED |
| Object | Advent |
—
|
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: Advent | Statement: [Approaching Christmas, focusesOnLiturgicalSeason, Advent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnLiturgicalSeason Context triple: [Approaching Christmas, focusesOnLiturgicalSeason, Advent]
-
A.
liturgicalCalendarFocus
Indicates the primary religious observance, theme, or commemoration that a liturgical calendar entry is centered on.
-
B.
liturgicalSeasonContext
chosen
Indicates the specific liturgical season within which a religious action, event, or text takes place or is understood.
-
C.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
D.
liturgicalSeasonRelation
Indicates a relationship between entities based on their association with, occurrence in, or relevance to a particular liturgical season.
-
E.
liturgicalSeasonVariation
Indicates that something changes or differs depending on the liturgical season within a religious calendar or worship cycle.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:16 p.m.