Triple
T27802104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restored Reformed Church |
E702272
|
entity |
| Predicate | worshipMusic |
P1105
|
FINISHED |
| Object | psalm singing |
—
|
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: psalm singing | Statement: [Restored Reformed Church, worshipMusic, psalm singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipMusic Context triple: [Restored Reformed Church, worshipMusic, psalm singing]
-
A.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
B.
worshipStyle
chosen
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
C.
worshipLeadership
Indicates that one entity holds a leadership role or primary responsibility in organizing or guiding worship activities for another entity or group.
-
D.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
-
E.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:35 p.m.