Triple
T4082730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alene Akins |
E87514
|
entity |
| Predicate | spouseRelationshipStatus |
P5173
|
FINISHED |
| Object | divorced from Larry King |
—
|
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: divorced from Larry King | Statement: [Alene Akins, spouseRelationshipStatus, divorced from Larry King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRelationshipStatus Context triple: [Alene Akins, spouseRelationshipStatus, divorced from Larry King]
-
A.
spouseStatus
chosen
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
B.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
D.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7933b481909bb3e02c6c04c8ee |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.