Triple
T5806973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonah |
E128768
|
entity |
| Predicate | preachedMessage |
P44623
|
FINISHED |
| Object | warning of impending destruction |
—
|
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: warning of impending destruction | Statement: [Jonah, preachedMessage, warning of impending destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preachedMessage Context triple: [Jonah, preachedMessage, warning of impending destruction]
-
A.
preached
chosen
Indicates that one entity delivered a religious or moral message or sermon to others.
-
B.
preachesFrom
Indicates that a person delivers a sermon, teaching, or religious message using a particular text, source, or location as the basis.
-
C.
sermonBy
Indicates that a sermon is delivered, authored, or given by a particular person or agent.
-
D.
spokePropheticallyAbout
Indicates that one entity made a statement or prediction about another entity or topic that is characterized as prophetic (foretelling future events or divine intentions).
-
E.
firstSermonEvent
Indicates the event during which an entity delivers its first sermon.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b15d8108190b434da42631c4e0c |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.