Triple
T6442743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transiturus de hoc mundo |
E138263
|
entity |
| Predicate | liturgicalFeastType |
P70665
|
FINISHED |
| Object | Solemnity |
—
|
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: Solemnity | Statement: [Transiturus de hoc mundo, liturgicalFeastType, Solemnity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalFeastType Context triple: [Transiturus de hoc mundo, liturgicalFeastType, Solemnity]
-
A.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
B.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
C.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
D.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
E.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.