Triple
T2214024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Helvetic Confession |
E50981
|
entity |
| Predicate | numberOfSacraments |
P1110
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Second Helvetic Confession, numberOfSacraments, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSacraments Context triple: [Second Helvetic Confession, numberOfSacraments, 2]
-
A.
sacramentNumber
chosen
Indicates the specific ordinal position or count assigned to a sacrament within a defined set or sequence of sacraments.
-
B.
includesSacrament
Indicates that one entity contains, involves, or incorporates a sacramental rite or practice as part of itself or its activities.
-
C.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
-
D.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
-
E.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfef875c8190b642736b4cc11d4c |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.