Triple
T29759037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epiphany (Timket) in adapted evangelical form |
E753710
|
entity |
| Predicate | usesWorshipStyle |
P1105
|
FINISHED |
| Object | Protestant worship |
—
|
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: Protestant worship | Statement: [Epiphany (Timket) in adapted evangelical form, usesWorshipStyle, Protestant worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWorshipStyle Context triple: [Epiphany (Timket) in adapted evangelical form, usesWorshipStyle, Protestant worship]
-
A.
worshipStyle
chosen
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
B.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
-
D.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
E.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f673cddb3881908c79b552d23521f3 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:30 p.m.