Triple
T16702311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacKenzie Scott |
E405881
|
entity |
| Predicate | publiclyAnnouncedDivorce |
P124295
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [MacKenzie Scott, publiclyAnnouncedDivorce, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyAnnouncedDivorce Context triple: [MacKenzie Scott, publiclyAnnouncedDivorce, 2019]
-
A.
divorceSettlementReportedAs
Indicates that a divorce settlement has been formally reported or recorded as a particular amount, status, or outcome.
-
B.
allowsDivorce
Indicates that one party permits or grants another party the right or ability to dissolve a marriage or marital union.
-
C.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
D.
postDissolutionStatus
Indicates the condition or state of an entity after a dissolution event has occurred.
-
E.
divorce
Indicates the legal dissolution of a marriage relationship between two spouses, ending their marital bond.
- F. None of above. chosen
Provenance (4 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383326d7081909ef4c3b724876513 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:19 a.m.