Triple
T26279644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Presence of Christ |
E660667
|
entity |
| Predicate | affirmedAs |
P31880
|
FINISHED |
| Object | substantial presence |
—
|
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: substantial presence | Statement: [Real Presence of Christ, affirmedAs, substantial presence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affirmedAs Context triple: [Real Presence of Christ, affirmedAs, substantial presence]
-
A.
confirmedAs
Indicates that one entity has been officially verified, recognized, or validated as being identical to or serving in the role of another entity.
-
B.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
C.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
D.
attestedAs
chosen
Indicates that something is documented, recorded, or certified as having a particular status, form, or property.
-
E.
authorityAffirmedBy
Indicates that the legitimacy or validity of an authority is confirmed, endorsed, or supported by another party or source.
- 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_69f60e734a088190ae453cc5dd222b40 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:59 p.m.