Triple
T18272086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi son of Jacob |
E437637
|
entity |
| Predicate | curseOrProphecy |
P22416
|
FINISHED |
| Object | Jacob’s prophecy of dispersion in Israel |
—
|
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: Jacob’s prophecy of dispersion in Israel | Statement: [Levi son of Jacob, curseOrProphecy, Jacob’s prophecy of dispersion in Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curseOrProphecy Context triple: [Levi son of Jacob, curseOrProphecy, Jacob’s prophecy of dispersion in Israel]
-
A.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
B.
typeOfProphecy
Indicates the specific category or kind of prophecy that a given prophetic statement or vision belongs to.
-
C.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
D.
subjectOfProphecy
chosen
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
E.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5004f0e7c8190a7206e193012a2d3 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.