Triple
T13574774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob |
E324251
|
entity |
| Predicate | deceptionEvent |
P7322
|
FINISHED |
| Object | obtaining Esau's blessing from Isaac |
—
|
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: obtaining Esau's blessing from Isaac | Statement: [Jacob, deceptionEvent, obtaining Esau's blessing from Isaac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deceptionEvent Context triple: [Jacob, deceptionEvent, obtaining Esau's blessing from Isaac]
-
A.
threatensDeceptionOf
Indicates that one entity poses or communicates a risk of deceiving or misleading another entity.
-
B.
eventUsedAsPretextFor
Indicates that one event is cited or leveraged as a justification or excuse for carrying out another action or event.
-
C.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
D.
tricked
chosen
Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
-
E.
fakedOwnDeath
Indicates that an entity deliberately staged or pretended their own death to deceive others.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.