Triple
T1586758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carin Göring |
E34082
|
entity |
| Predicate | spouseEndTimeWithNilsVonKantzow |
P493
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Carin Göring, spouseEndTimeWithNilsVonKantzow, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseEndTimeWithNilsVonKantzow Context triple: [Carin Göring, spouseEndTimeWithNilsVonKantzow, 1922]
-
A.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
spouseRelationshipEnd
chosen
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
C.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
-
D.
coSpouse
Indicates that two individuals are married to each other as spouses.
-
E.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.