Triple
T12896281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantata IV |
E308500
|
entity |
| Predicate | associatedLiturgicalDay |
P86735
|
FINISHED |
| Object | 1 January |
—
|
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: 1 January | Statement: [Cantata IV, associatedLiturgicalDay, 1 January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLiturgicalDay Context triple: [Cantata IV, associatedLiturgicalDay, 1 January]
-
A.
liturgicalFeastDay
chosen
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
B.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
C.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
D.
liturgicalMoment
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
-
E.
liturgicalDayPosition
Indicates the specific placement or order of a liturgical day within a liturgical calendar, season, or sequence of observances.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.