Triple
T35513803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Morton Carroll |
E1026355
|
entity |
| Predicate | spouseMentalState |
P196759
|
FINISHED |
| Object | psychologically unstable |
—
|
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: psychologically unstable | Statement: [Sally Morton Carroll, spouseMentalState, psychologically unstable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseMentalState Context triple: [Sally Morton Carroll, spouseMentalState, psychologically unstable]
-
A.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
B.
spouseState
Indicates the marital status or condition of a person’s spouse in relation to them.
-
C.
spouseInQuestion
Indicates that the referenced person is the spouse of the primary entity being discussed or queried.
-
D.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
E.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69fe673905408190a2ae68c2c9563403 |
completed | May 8, 2026, 10:44 p.m. |
Created at: May 3, 2026, 4:04 p.m.