Triple
T331519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light of the World |
E6634
|
entity |
| Predicate | themeIn |
P7671
|
FINISHED |
| Object | Christian sermons on evangelism |
—
|
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: Christian sermons on evangelism | Statement: [Light of the World, themeIn, Christian sermons on evangelism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeIn Context triple: [Light of the World, themeIn, Christian sermons on evangelism]
-
A.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
B.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
C.
themeContrast
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
-
D.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
E.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaafd1a48190a6d001af3c2a5318 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.