Triple
T38320475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martyn Eaden |
E1036651
|
entity |
| Predicate | filedForDivorce |
P190639
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Martyn Eaden, filedForDivorce, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filedForDivorce Context triple: [Martyn Eaden, filedForDivorce, 2014]
-
A.
divorce
Indicates the legal dissolution of a marriage relationship between two spouses, ending their marital bond.
-
B.
allowsDivorce
Indicates that one party permits or grants another party the right or ability to dissolve a marriage or marital union.
-
C.
partnerInDivorce
Indicates that two individuals are parties on opposing sides in the same divorce proceeding.
-
D.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
E.
publiclyAnnouncedDivorce
Indicates that an individual or entity has made a formal, public declaration that a marital or partnership relationship has ended or will end in divorce.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.