Triple
T47907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Baptism |
E941
|
entity |
| Predicate | involvesRitualAction |
P1256
|
FINISHED |
| Object | immersion in water |
—
|
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: immersion in water | Statement: [Holy Baptism, involvesRitualAction, immersion in water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRitualAction Context triple: [Holy Baptism, involvesRitualAction, immersion in water]
-
A.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
B.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.