Triple
T4405692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judah son of Jacob |
E93726
|
entity |
| Predicate | blessingReceived |
P20739
|
FINISHED |
| Object | Genesis 49:8–12 blessing from Jacob |
—
|
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: Genesis 49:8–12 blessing from Jacob | Statement: [Judah son of Jacob, blessingReceived, Genesis 49:8–12 blessing from Jacob]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blessingReceived Context triple: [Judah son of Jacob, blessingReceived, Genesis 49:8–12 blessing from Jacob]
-
A.
blessedBy
chosen
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
B.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
C.
blessingRecordedIn
Indicates that a blessing event or act has been documented or preserved within a specific record, text, or medium.
-
D.
firstBlessing
Indicates that an entity is the initial recipient or instance of a blessing in relation to another entity or context.
-
E.
fourthBlessing
Indicates that an entity receives or is associated with the fourth in a sequence of blessings.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b35489f6948190a4b2c259f64b4abf |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.