Triple
T28825700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen Sullivan Crothers |
E727895
|
entity |
| Predicate | endOfMarriageCause |
P56331
|
FINISHED |
| Object | death of spouse |
—
|
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: death of spouse | Statement: [Helen Sullivan Crothers, endOfMarriageCause, death of spouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfMarriageCause Context triple: [Helen Sullivan Crothers, endOfMarriageCause, death of spouse]
-
A.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
B.
marriageEndedBy
chosen
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
C.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
D.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
E.
marriageOutcome
Indicates the result or status that follows from a marriage, such as whether it continues, ends, or changes form.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:36 a.m.