Triple
T14060585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uriah son of Shemaiah |
E338332
|
entity |
| Predicate | propheticTheme |
P54609
|
FINISHED |
| Object | judgment against Judah |
—
|
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: judgment against Judah | Statement: [Uriah son of Shemaiah, propheticTheme, judgment against Judah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propheticTheme Context triple: [Uriah son of Shemaiah, propheticTheme, judgment against Judah]
-
A.
prophecyTheme
chosen
Indicates that the relationship or action centers on the theme, content, or subject matter of a prophecy.
-
B.
propheticActivity
Indicates engaging in or being associated with acts of prophecy, such as receiving, delivering, or performing messages believed to be divinely inspired.
-
C.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
D.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
E.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.