Triple
T34089052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Echo in the Darkness |
E874252
|
entity |
| Predicate | hasChristianContent |
P24743
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [An Echo in the Darkness, hasChristianContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianContent Context triple: [An Echo in the Darkness, hasChristianContent, true]
-
A.
containsAdultContent
Indicates that the referenced item includes material intended for adults, such as explicit sexual, violent, or otherwise age-restricted content.
-
B.
hasHalakhicContent
Indicates that something contains, expresses, or is concerned with content related to Jewish law (halakha).
-
C.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
D.
hasReligiousTheme
chosen
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
E.
hasReligiousProgramming
Indicates that an entity provides, features, or includes content or activities related to religious themes, practices, or teachings.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 1, 2026, 1:52 a.m.