Triple
T26279629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Presence of Christ |
E660667
|
entity |
| Predicate | teachesPresenceOf |
P131491
|
FINISHED |
| Object | Body 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: Body of Christ | Statement: [Real Presence of Christ, teachesPresenceOf, Body of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teachesPresenceOf Context triple: [Real Presence of Christ, teachesPresenceOf, Body of Christ]
-
A.
meetsInPresenceOf
Indicates that two or more entities meet or interact while another specified entity is present as a witness, chaperone, or contextual participant.
-
B.
containsTeachingOf
chosen
Indicates that one entity includes, embodies, or presents the teaching, doctrine, or instructional content associated with another entity.
-
C.
teachesAbout
Indicates that one entity provides instruction or information to another entity on a particular subject or topic.
-
D.
traditionalPresenceIn
Indicates that an entity has a customary or historically established presence within a particular place, context, or setting.
-
E.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 9:59 p.m.