Triple
T430797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastertide |
E9706
|
entity |
| Predicate | prayerFocus |
P11162
|
FINISHED |
| Object | joy, renewal, and mission |
—
|
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: joy, renewal, and mission | Statement: [Eastertide, prayerFocus, joy, renewal, and mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerFocus Context triple: [Eastertide, prayerFocus, joy, renewal, and mission]
-
A.
spiritualDiscipline
Indicates a relationship where an entity engages in or practices a form of spiritual training, exercise, or regimen aimed at cultivating spiritual growth or character.
-
B.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
C.
isAddressedInPrayer
chosen
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
-
D.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
E.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.