Triple
T29140662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praise Be! (religious television programme) |
E738621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious television programme |
C36591
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: religious television programme Context triple: [Praise Be! (religious television programme), instanceOf, religious television programme]
-
A.
religious television series
chosen
A religious television series is a serialized program that explores spiritual themes, doctrines, or faith-based narratives, often aiming to inspire, educate, or reflect the beliefs and practices of a particular religious tradition.
-
B.
religious broadcast
A religious broadcast is a media program transmitted via radio, television, or digital platforms that communicates faith-based messages, teachings, worship services, or spiritual content to a remote audience.
-
C.
religious broadcaster
A religious broadcaster is an individual or organization that produces and transmits faith-based content through radio, television, or digital media to inform, inspire, and engage religious audiences.
-
D.
religious media organization
A religious media organization is an entity that produces, curates, and distributes content across various media platforms to promote, explain, or support specific religious beliefs, practices, or communities.
-
E.
religious conference
A religious conference is a structured gathering where individuals and groups come together to explore, discuss, and deepen understanding of faith-related topics through presentations, worship, and communal activities.
- F. None of above.
Provenance (1 batch)
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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:36 a.m.