Triple
T30721978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetrapolitan Confession |
E782176
|
entity |
| Predicate | positionOnLordSupper |
P189999
|
FINISHED |
| Object | symbolic or spiritual presence of Christ |
—
|
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: symbolic or spiritual presence of Christ | Statement: [Tetrapolitan Confession, positionOnLordSupper, symbolic or spiritual presence of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLordSupper Context triple: [Tetrapolitan Confession, positionOnLordSupper, symbolic or spiritual presence of Christ]
-
A.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
B.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
C.
positionInHolyWeek
Indicates the specific place or order that a day, event, or observance occupies within the sequence of days in Holy Week.
-
D.
sacramentalPosition
chosen
Indicates the role or status an entity holds within a sacramental context or ritual.
-
E.
positionOnJesus
Indicates a stance, view, or opinion that an entity holds regarding Jesus.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 8:36 p.m.