Triple
T38558681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Church |
E925314
|
entity |
| Predicate | sacramentsInclude |
P13034
|
FINISHED |
| Object | Baptism |
—
|
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: Baptism | Statement: [Roman Church, sacramentsInclude, Baptism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacramentsInclude Context triple: [Roman Church, sacramentsInclude, Baptism]
-
A.
coreSacraments
Indicates that the specified religious rites are recognized as the fundamental or primary sacraments within a given religious tradition.
-
B.
includesSacrament
chosen
Indicates that one entity contains, involves, or incorporates a sacramental rite or practice as part of itself or its activities.
-
C.
celebratesSacramentsAccordingTo
Indicates that an individual or group performs or observes the sacraments in accordance with a specified rite, tradition, or set of liturgical norms.
-
D.
sacramentFunction
Indicates that one entity serves as a religious sacrament or sacred rite performed or administered in relation to another entity.
-
E.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd31ece7c819080823c6006f4eaa2 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.