Triple
T8280564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | people of Lot |
E193658
|
entity |
| Predicate | committedSin |
P32803
|
FINISHED |
| Object | sexual immorality |
—
|
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: sexual immorality | Statement: [people of Lot, committedSin, sexual immorality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committedSin Context triple: [people of Lot, committedSin, sexual immorality]
-
A.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
B.
hasTransgression
chosen
Indicates that one entity has committed, is responsible for, or is associated with a violation, offense, or wrongdoing in relation to another entity or rule.
-
C.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
-
D.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
E.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ee66e48190af7058b14f3daac9 |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.