Triple
T33394943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogation of the Ninevites |
E855146
|
entity |
| Predicate | isBasedOnEvent |
P3224
|
FINISHED |
| Object | Ninevites’ response to Jonah’s preaching |
—
|
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: Ninevites’ response to Jonah’s preaching | Statement: [Rogation of the Ninevites, isBasedOnEvent, Ninevites’ response to Jonah’s preaching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBasedOnEvent Context triple: [Rogation of the Ninevites, isBasedOnEvent, Ninevites’ response to Jonah’s preaching]
-
A.
basedOnEvent
chosen
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
B.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
C.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
D.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.