Triple
T33099404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morwenna Chynoweth |
E847000
|
entity |
| Predicate | forcedSpouse |
P176111
|
FINISHED |
| Object | Reverend Osborne Whitworth |
—
|
NE NERFINISHED |
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: Reverend Osborne Whitworth | Statement: [Morwenna Chynoweth, forcedSpouse, Reverend Osborne Whitworth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedSpouse Context triple: [Morwenna Chynoweth, forcedSpouse, Reverend Osborne Whitworth]
-
A.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
E.
intendedSpouse
Indicates that one person is planned or expected to become the spouse of another, typically through an intended or future marriage.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:26 a.m.