Triple
T31856800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam and Eve |
E813217
|
entity |
| Predicate | tempter |
P59155
|
FINISHED |
| Object | serpent |
—
|
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: serpent | Statement: [Adam and Eve, tempter, serpent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempter Context triple: [Adam and Eve, tempter, serpent]
-
A.
temptation
Indicates a situation or influence that strongly urges or entices an entity to perform an action, typically one that is considered wrong, unwise, or against their better judgment.
-
B.
involvesTempter
chosen
Indicates that the situation or event includes an entity acting as a tempter, attempting to entice or lure another into a particular action or state.
-
C.
thirdTemptation
Indicates the relationship in which an entity is subjected to or involved in the third in a sequence of temptations or tests.
-
D.
secondTemptation
Indicates a relationship where an entity is subjected to or engages in a second instance of temptation, following an initial tempting event.
-
E.
firstTemptation
Indicates the initial instance in which an entity is enticed or urged toward a potentially wrong, risky, or forbidden action.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b06a8fdc819090bbb2d491bb2a35 |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:52 p.m.