Triple
T4761799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fall of Man |
E105713
|
entity |
| Predicate | involvesTempter |
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: [The Fall of Man, involvesTempter, serpent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTempter Context triple: [The Fall of Man, involvesTempter, serpent]
-
A.
thirdTemptation
Indicates the relationship in which an entity is subjected to or involved in the third in a sequence of temptations or tests.
-
B.
hasNumberOfTemptations
Indicates the specific count of temptations associated with an entity or situation.
-
C.
firstTemptation
Indicates the initial instance in which an entity is enticed or urged toward a potentially wrong, risky, or forbidden action.
-
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.
seducedBy
Indicates that one entity has been romantically or sexually enticed, persuaded, or lured into intimacy or a relationship by another entity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:20 p.m.