Triple
T16803044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Lutheran Church |
E408404
|
entity |
| Predicate | worshipElement |
P11149
|
FINISHED |
| Object | preaching of the Word |
—
|
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: preaching of the Word | Statement: [Evangelical Lutheran Church, worshipElement, preaching of the Word]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipElement Context triple: [Evangelical Lutheran Church, worshipElement, preaching of the Word]
-
A.
worshipLinkedTo
Indicates that an act or practice of worship is connected or associated with a particular entity, concept, or context.
-
B.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
C.
worshipSymbol
Indicates a relationship where one entity venerates, honors, or directs religious devotion toward another entity as a sacred symbol.
-
D.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
worshipArea
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ca46f88190b56e81d75012496c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.