Triple
T19074843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Reconciliation |
E466877
|
entity |
| Predicate | liturgicalFormIncludes |
P134221
|
FINISHED |
| Object | sign of the cross |
—
|
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: sign of the cross | Statement: [First Reconciliation, liturgicalFormIncludes, sign of the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalFormIncludes Context triple: [First Reconciliation, liturgicalFormIncludes, sign of the cross]
-
A.
liturgicalFormTermUsed
Indicates that a particular liturgical form is referred to or designated by a specific term.
-
B.
hasPrimaryLiturgicalForm
Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious practice.
-
C.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
-
D.
hasLiturgicalNature
Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
-
E.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
- F. None of above. chosen
Provenance (4 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.