Triple
T5058465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cain |
E113963
|
entity |
| Predicate | offeringOutcome |
P61014
|
FINISHED |
| Object | rejected by God |
—
|
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: rejected by God | Statement: [Cain, offeringOutcome, rejected by God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeringOutcome Context triple: [Cain, offeringOutcome, rejected by God]
-
A.
offersOutcome
Indicates that one entity provides or makes available a particular result, consequence, or benefit to another entity.
-
B.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
C.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
D.
offeredCrownOutcome
Indicates the outcome or result that followed from an offer of a crown or rulership being made to someone.
-
E.
offersAward
Indicates that one entity grants or makes available an award or prize to 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74523434819092b8b15992073b5b |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:38 p.m.