Triple
T25000670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Stilwell Edison |
E625708
|
entity |
| Predicate | spouseLaterMarried |
P139882
|
FINISHED |
| Object | Mina Miller Edison |
—
|
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: Mina Miller Edison | Statement: [Mary Stilwell Edison, spouseLaterMarried, Mina Miller Edison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseLaterMarried Context triple: [Mary Stilwell Edison, spouseLaterMarried, Mina Miller Edison]
-
A.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
-
B.
subsequentSpouse
chosen
Indicates that one person is a later spouse of another, following a previous marriage involving at least one of them.
-
C.
fiancéeLaterMarried
Indicates that a person who was once engaged to another person later went on to marry that same individual.
-
D.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
E.
laterMarriedName
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:04 a.m.