Triple
T4079471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Way of Sorrows |
E87441
|
entity |
| Predicate | isOftenPrayedIn |
P21327
|
FINISHED |
| Object | churches |
—
|
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: churches | Statement: [Way of Sorrows, isOftenPrayedIn, churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPrayedIn Context triple: [Way of Sorrows, isOftenPrayedIn, churches]
-
A.
isAddressedInPrayer
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
-
B.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
C.
associatedPrayer
chosen
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
D.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
E.
canBePrayedInCongregation
Indicates that the action or ritual can be performed collectively as a group worship or prayer, rather than only individually.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.