Triple
T4904725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathan |
E109886
|
entity |
| Predicate | rebukedFor |
P805
|
FINISHED |
| Object | David’s adultery with Bathsheba |
—
|
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: David’s adultery with Bathsheba | Statement: [Nathan, rebukedFor, David’s adultery with Bathsheba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebukedFor Context triple: [Nathan, rebukedFor, David’s adultery with Bathsheba]
-
A.
criticizedFor
chosen
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
D.
blamedOn
Indicates that responsibility or fault for something is assigned to a particular entity.
-
E.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.