Triple
T31393835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Pond Parker II |
E800808
|
entity |
| Predicate | causeOfMaritalStrain |
P76645
|
FINISHED |
| Object | alcohol use |
—
|
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: alcohol use | Statement: [Edwin Pond Parker II, causeOfMaritalStrain, alcohol use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfMaritalStrain Context triple: [Edwin Pond Parker II, causeOfMaritalStrain, alcohol use]
-
A.
maritalIssue
Indicates a relationship where there is conflict, dissatisfaction, or significant strain within a marital or committed partnership.
-
B.
effectOnMaritalRelations
chosen
Indicates how an action, event, or condition influences the quality, stability, or dynamics of marital relationships between partners.
-
C.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
D.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
E.
causeOfNonMarriage
Indicates the reason or factor that prevents or has prevented two entities from being married to each other.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 9:19 p.m.