Triple
T8384597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Subtle Enemies of Holiness |
E197781
|
entity |
| Predicate | associatedDocumentTheme |
P56598
|
FINISHED |
| Object | call to everyday holiness |
—
|
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: call to everyday holiness | Statement: [Two Subtle Enemies of Holiness, associatedDocumentTheme, call to everyday holiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDocumentTheme Context triple: [Two Subtle Enemies of Holiness, associatedDocumentTheme, call to everyday holiness]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
primaryThemeAssociation
Indicates that one entity is the main or central theme associated with another entity.
-
C.
associatedWithWorkTheme
chosen
Indicates a relationship where something is connected or related to a particular work theme or subject matter.
-
D.
signatureTheme
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
-
E.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e03eb08190a458c9caa0524e0f |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.