Triple
T1090226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicia Nash |
E24144
|
entity |
| Predicate | remarriageToSameSpouse |
P23362
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Alicia Nash, remarriageToSameSpouse, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remarriageToSameSpouse Context triple: [Alicia Nash, remarriageToSameSpouse, 1970s]
-
A.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
B.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
C.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
D.
numberOfMarriagesOfSpouse
Indicates the total count of times the referenced spouse has been married.
-
E.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b980c8448190b08c3a9a7e7f4e85 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:42 p.m.