Triple
T21419101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miriam Raymond |
E528383
|
entity |
| Predicate | endOfMarriageReason |
P13503
|
FINISHED |
| Object | divorce |
—
|
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: divorce | Statement: [Miriam Raymond, endOfMarriageReason, divorce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfMarriageReason Context triple: [Miriam Raymond, endOfMarriageReason, divorce]
-
A.
divorceReason
chosen
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
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.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
D.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
E.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2ccddc08190b4f66fa6ccda41e2 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:47 p.m.