Triple
T17742826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gad son of Jacob |
E442905
|
entity |
| Predicate | blessingFromJacobLocation |
P128824
|
FINISHED |
| Object | Genesis 49:19 |
—
|
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:19 | Statement: [Gad son of Jacob, blessingFromJacobLocation, Genesis 49:19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blessingFromJacobLocation Context triple: [Gad son of Jacob, blessingFromJacobLocation, Genesis 49:19]
-
A.
describedAsInJacobBlessing
Indicates that an entity is characterized or portrayed in the specific manner it appears within Jacob’s blessing narrative (e.g., in Genesis 49).
-
B.
blessingFromMosesText
Indicates that the text expresses or contains a blessing given by Moses.
-
C.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
D.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
E.
firstBlessing
Indicates that an entity is the initial recipient or instance of a blessing in relation to another entity or context.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ace58988190b927ca29af7a8b77 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:09 a.m.