Triple
T38088856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Wife’s Relations |
E951053
|
entity |
| Predicate | hasMaritalPlot |
—
|
GENERATED |
| Object | man mistakenly married into a tough family |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritalPlot Context triple: [My Wife’s Relations, hasMaritalPlot, man mistakenly married into a tough family]
-
A.
hasMarriagePlot
chosen
Indicates that the work’s narrative centrally involves courtship, romantic relationships, or the progression toward marriage as a key plot element.
-
B.
hasMaritalInfidelitySubplot
Indicates that the work includes a subplot involving a character engaging in romantic or sexual infidelity within a marriage.
-
C.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
-
D.
hasMaritalFunction
Indicates that one entity serves a role or performs a function within the context of a marital relationship or institution.
-
E.
marriageDepictedIn
Indicates that a specific marriage is represented or shown within a particular work, medium, or depiction.
- F. None of above.
Provenance (1 batch)
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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.