Triple
T19052838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Porter |
E466307
|
entity |
| Predicate | maritalStatusBeforeMarriageToSamuelJohnson |
P47002
|
FINISHED |
| Object | widow |
—
|
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: widow | Statement: [Elizabeth Porter, maritalStatusBeforeMarriageToSamuelJohnson, widow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusBeforeMarriageToSamuelJohnson Context triple: [Elizabeth Porter, maritalStatusBeforeMarriageToSamuelJohnson, widow]
-
A.
spouseStatusAtMarriage
chosen
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
B.
maritalStatusBeforeRenunciation
Indicates the marital status a person had prior to formally renouncing a role, status, or affiliation.
-
C.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
D.
legalStatusOfMarriageToJohn
Indicates the legal status or validity of a person’s marriage in relation to John.
-
E.
marriageToHenryVIIIStatus
Indicates the status or condition of an entity’s marriage relationship to Henry VIII (e.g., current, former, annulled, pending, etc.).
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc03dfa08190924a1b8073364fa1 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.