Triple
T29193329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace Austin |
E740054
|
entity |
| Predicate | endCauseOfMarriage |
P62586
|
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: [Wallace Austin, endCauseOfMarriage, divorce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endCauseOfMarriage Context triple: [Wallace Austin, endCauseOfMarriage, divorce]
-
A.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
B.
causeOfNonMarriage
Indicates the reason or factor that prevents or has prevented two entities from being married to each other.
-
C.
politicalPurposeOfMarriage
Indicates that a marriage is entered into or used primarily for political objectives, such as gaining power, forming alliances, or influencing governance.
-
D.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
-
E.
marriageResolvedBy
chosen
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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638cf96081909686087393f5d8d1 |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:03 p.m.