Triple
T18323397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Caroline of Brunswick |
E438939
|
entity |
| Predicate | separatedFromSpouse |
P493
|
FINISHED |
| Object | 1796 |
—
|
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: 1796 | Statement: [Queen Caroline of Brunswick, separatedFromSpouse, 1796]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFromSpouse Context triple: [Queen Caroline of Brunswick, separatedFromSpouse, 1796]
-
A.
spouseRelationshipEnd
chosen
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
B.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
C.
divorce
Indicates the legal dissolution of a marriage relationship between two spouses, ending their marital bond.
-
D.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
E.
hasDissolvedOrSeparatedFrom
Indicates that one entity has formally ended, dissolved, or separated its prior association, union, or affiliation with another entity.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa886508190902ffc26b30731ae |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.