Triple
T189915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confirmation |
E3695
|
entity |
| Predicate | liturgicalSeasonOftenUsed |
P4415
|
FINISHED |
| Object | Easter season |
—
|
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: Easter season | Statement: [Confirmation, liturgicalSeasonOftenUsed, Easter season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalSeasonOftenUsed Context triple: [Confirmation, liturgicalSeasonOftenUsed, Easter season]
-
A.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
-
B.
usedInSeason
chosen
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
hasLiturgicalColor
Indicates that something is associated with a specific liturgical color used in religious rites or ceremonies.
-
D.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
E.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2594c385481909e1e088e45c460a4 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25673ce3c8190b1a3df5b814a0595 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.