Triple
T4852564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abner |
E108449
|
entity |
| Predicate | reactionToAccusation |
P59948
|
FINISHED |
| Object | broke with Ish-bosheth |
—
|
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: broke with Ish-bosheth | Statement: [Abner, reactionToAccusation, broke with Ish-bosheth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionToAccusation Context triple: [Abner, reactionToAccusation, broke with Ish-bosheth]
-
A.
reactionToAffair
Indicates how an entity responds emotionally or behaviorally to an affair or infidelity involving another entity.
-
B.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
C.
accusationTarget
Indicates that one entity is the object or recipient of an accusation made by another entity.
-
D.
spouseAccusation
Indicates that one spouse has accused the other spouse of some wrongdoing, misconduct, or blameworthy action.
-
E.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:26 p.m.