Triple
T20805089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinquagesima Sunday |
E512133
|
entity |
| Predicate | traditionalGospelReading |
P74369
|
FINISHED |
| Object | Luke 18:31–43 |
—
|
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: Luke 18:31–43 | Statement: [Quinquagesima Sunday, traditionalGospelReading, Luke 18:31–43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalGospelReading Context triple: [Quinquagesima Sunday, traditionalGospelReading, Luke 18:31–43]
-
A.
gospelReadingFrom
chosen
Indicates that a particular gospel reading is taken from or sourced in a specified scriptural passage or book.
-
B.
scriptureRead
Indicates that an entity reads, studies, or engages with a religious or sacred text.
-
C.
gospelEpisode
Indicates that one entity is an episode or segment within a gospel narrative or gospel-related series associated with another entity.
-
D.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
E.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ce6420819091792ffaa3c46c53 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.