Triple
T4852710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Absalom’s revenge on Amnon |
E108452
|
entity |
| Predicate | isConnectedToProphecy |
P20088
|
FINISHED |
| Object | Nathan’s prophecy of calamity in David’s house |
—
|
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: Nathan’s prophecy of calamity in David’s house | Statement: [Absalom’s revenge on Amnon, isConnectedToProphecy, Nathan’s prophecy of calamity in David’s house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedToProphecy Context triple: [Absalom’s revenge on Amnon, isConnectedToProphecy, Nathan’s prophecy of calamity in David’s house]
-
A.
linkedToProphet
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
-
B.
interpretedAsProphecyBy
Indicates that something (such as an event, statement, or sign) is understood or treated by someone as a prophecy or predictive message about the future.
-
C.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
D.
containsProphecyAbout
chosen
Indicates that one entity includes or conveys a prediction or foretelling specifically concerning another entity.
-
E.
prophecyOverheardBy
Indicates that a prophecy was heard or accidentally listened to by a particular entity, without necessarily being its intended recipient.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.