Triple
T1386579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Gospel |
E29858
|
entity |
| Predicate | devotionalCharacter |
P21326
|
FINISHED |
| Object | quasi-devotional addition to the Mass |
—
|
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: quasi-devotional addition to the Mass | Statement: [Last Gospel, devotionalCharacter, quasi-devotional addition to the Mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalCharacter Context triple: [Last Gospel, devotionalCharacter, quasi-devotional addition to the Mass]
-
A.
associatedDevotion
chosen
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.