Triple
T26124855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Law and the Gospel |
E659071
|
entity |
| Predicate | sideRepresentingGospel |
P160343
|
FINISHED |
| Object | right side |
—
|
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: right side | Statement: [The Law and the Gospel, sideRepresentingGospel, right side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideRepresentingGospel Context triple: [The Law and the Gospel, sideRepresentingGospel, right side]
-
A.
linkedToGospel
Indicates a relationship where something is connected or related to the gospel, typically in content, origin, or thematic focus.
-
B.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
C.
isGospelInfluenced
Indicates that one entity (such as a work, style, or performance) is influenced in its characteristics, form, or content by gospel music or gospel traditions.
-
D.
gospelDescription
Indicates that one entity provides a summary or explanation of the core message, content, or significance of the gospel concerning another entity.
-
E.
gospelReadingFrom
Indicates that a particular gospel reading is taken from or sourced in a specified scriptural passage or book.
- F. None of above. chosen
Provenance (4 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60ad0714c8190b22f7a912cad364e |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:11 p.m.