Triple
T951481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam |
E20531
|
entity |
| Predicate | consequenceOfDisobedience |
P812
|
FINISHED |
| Object | expulsion from Eden |
—
|
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: expulsion from Eden | Statement: [Adam, consequenceOfDisobedience, expulsion from Eden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfDisobedience Context triple: [Adam, consequenceOfDisobedience, expulsion from Eden]
-
A.
religiousConsequence
Indicates a relationship where one event, action, or state leads to an outcome specifically defined or understood in religious terms (such as divine reward, punishment, obligation, or spiritual effect).
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
E.
obeysLaw
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d757d08190a475cf47febd05ae |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.