Triple
T34865569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VI Sunday of Easter |
E1004998
|
entity |
| Predicate | hasCalendarContext |
P197024
|
FINISHED |
| Object | Christian liturgical calendar |
—
|
NE NERFINISHED |
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: Christian liturgical calendar | Statement: [VI Sunday of Easter, hasCalendarContext, Christian liturgical calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarContext Context triple: [VI Sunday of Easter, hasCalendarContext, Christian liturgical calendar]
-
A.
hasCalendarFunction
Indicates that an entity possesses or supports a calendar-related capability or functionality.
-
B.
hasCalendarStructure
Indicates that something possesses or follows a specific calendar-based organizational structure (e.g., dates, months, or scheduling framework).
-
C.
hasDateContext
Indicates that something is associated with, constrained by, or interpreted within a specific date or time-related context.
-
D.
hasCalendarAssociation
chosen
Indicates that there is a defined relationship or linkage between an entity and a calendar or calendar-related item (such as an event, schedule, or time period).
-
E.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4 p.m.