Triple
T19362807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotte Lenya |
E484322
|
entity |
| Predicate | remarriageEnd |
P92796
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Lotte Lenya, remarriageEnd, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remarriageEnd Context triple: [Lotte Lenya, remarriageEnd, 1950]
-
A.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
B.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
C.
remarriageToSameSpouse
Indicates that an individual has legally remarried a person who was previously their spouse.
-
D.
refusedRemarriageTo
Indicates that one entity declined or rejected entering into a subsequent marriage with another entity.
-
E.
endTime (marriage)
chosen
Indicates the point in time at which the marriage relationship is considered to have ended.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a897008190a2c62a50ca60de2d |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.