Triple
T11060729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amma Sarah |
E261499
|
entity |
| Predicate | hasSayingTheme |
P97577
|
FINISHED |
| Object | spiritual warfare |
—
|
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: spiritual warfare | Statement: [Amma Sarah, hasSayingTheme, spiritual warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSayingTheme Context triple: [Amma Sarah, hasSayingTheme, spiritual warfare]
-
A.
hasThemeInStory
Indicates that a particular theme is present or plays a significant role within a given story.
-
B.
hasPersonalThemes
Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
-
C.
includesSaying
Indicates that one entity (such as a text, speech, or communication) contains or incorporates a particular saying, phrase, or quoted expression.
-
D.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
E.
hasMotiveTheme
Indicates that an action, event, or situation is associated with a central motivating theme or underlying driving idea.
- F. None of above. chosen
Provenance (4 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798e991848190b07c2f48dae38681 |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.