Triple
T34511668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed churches in Germany |
E886038
|
entity |
| Predicate | worshipCharacteristic |
P1105
|
FINISHED |
| Object | emphasis on preaching |
—
|
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: emphasis on preaching | Statement: [Reformed churches in Germany, worshipCharacteristic, emphasis on preaching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipCharacteristic Context triple: [Reformed churches in Germany, worshipCharacteristic, emphasis on preaching]
-
A.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
B.
worshipStyle
chosen
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipBy
Indicates that one entity is the object of religious reverence, devotion, or adoration performed by another entity.
-
E.
worshipCharacter
Indicates that one entity regards another as sacred or divine and performs acts of reverence, devotion, or religious honor toward them.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.