Triple
T19802004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dianne Bock Stern |
E475703
|
entity |
| Predicate | spouseLifeEvent |
P85988
|
FINISHED |
| Object | David Stern died on January 1, 2020 |
—
|
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 Stern died on January 1, 2020 | Statement: [Dianne Bock Stern, spouseLifeEvent, David Stern died on January 1, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseLifeEvent Context triple: [Dianne Bock Stern, spouseLifeEvent, David Stern died on January 1, 2020]
-
A.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
-
B.
spouseAtEvent
Indicates that two individuals are spouses who are present together at a specific event.
-
C.
hasSpouseNotableEvent
chosen
Indicates that a person’s spouse is associated with a notable event related to that person.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654257cb4819096fb2aa5d1f7fbb0 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.