Triple
T1340890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinners in the Hands of an Angry God |
E28460
|
entity |
| Predicate | imageUsed |
P17123
|
FINISHED |
| Object | spider held over a fire |
—
|
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: spider held over a fire | Statement: [Sinners in the Hands of an Angry God, imageUsed, spider held over a fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageUsed Context triple: [Sinners in the Hands of an Angry God, imageUsed, spider held over a fire]
-
A.
usesImageryOf
chosen
Indicates that one entity employs or incorporates visual or sensory imagery that depicts, references, or symbolically represents another entity.
-
B.
publicImage
Indicates how an entity is perceived or represented by the general public or broader audience.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
usedByMedia
Indicates that something is employed or utilized by media organizations or media-related channels.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21490488190b4281a16c87677d1 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.