Triple
T25869672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Church |
E651715
|
entity |
| Predicate | liturgicalPracticeIncludes |
P88754
|
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: [New Church, liturgicalPracticeIncludes, baptism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalPracticeIncludes Context triple: [New Church, liturgicalPracticeIncludes, baptism]
-
A.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
B.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
C.
liturgicalActivities
chosen
Indicates involvement in or performance of formal religious or liturgical rites, ceremonies, or related devotional practices.
-
D.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
liturgicalServices
Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity or 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602db41d08190b3c1b0b7d904b4bc |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:10 a.m.