Triple
T954404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dina bint Abdul-Hamid |
E20593
|
entity |
| Predicate | causeOfEndOfMarriage |
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: [Dina bint Abdul-Hamid, causeOfEndOfMarriage, divorce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEndOfMarriage Context triple: [Dina bint Abdul-Hamid, causeOfEndOfMarriage, divorce]
-
A.
divorceReason
chosen
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
B.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
maritalBasis
Indicates that the relationship or status in question is founded on, justified by, or determined due to a marital relationship between the involved entities.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3da8d508190b56b29d7f235d2c4 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.