Triple
T29363222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sara Northrup Hollister |
E744646
|
entity |
| Predicate | divorceReasonAlleged |
P13503
|
FINISHED |
| Object | cruelty |
—
|
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: cruelty | Statement: [Sara Northrup Hollister, divorceReasonAlleged, cruelty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divorceReasonAlleged Context triple: [Sara Northrup Hollister, divorceReasonAlleged, cruelty]
-
A.
divorceReason
chosen
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
B.
divorce
Indicates the legal dissolution of a marriage relationship between two spouses, ending their marital bond.
-
C.
spouseAccusation
Indicates that one spouse has accused the other spouse of some wrongdoing, misconduct, or blameworthy action.
-
D.
allowsDivorce
Indicates that one party permits or grants another party the right or ability to dissolve a marriage or marital union.
-
E.
divorceSettlementReportedAs
Indicates that a divorce settlement has been formally reported or recorded as a particular amount, status, or outcome.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6698a5c608190b80127eb9605ab60 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:20 p.m.