Triple
T4390375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Barker |
E99346
|
entity |
| Predicate | marriageEndedBy |
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: [Bob Barker, marriageEndedBy, death of spouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageEndedBy Context triple: [Bob Barker, marriageEndedBy, death of spouse]
-
A.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
B.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
D.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35282cb2c8190856da20bb87e88ff |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.