Triple
T36653458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelley Ashby |
E904926
|
entity |
| Predicate | spouseRepresentsState |
P37617
|
FINISHED |
| Object | Kentucky |
—
|
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: Kentucky | Statement: [Kelley Ashby, spouseRepresentsState, Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRepresentsState Context triple: [Kelley Ashby, spouseRepresentsState, Kentucky]
-
A.
spouseState
Indicates the marital status or condition of a person’s spouse in relation to them.
-
B.
spouseRepresents
Indicates that one spouse formally acts on behalf of, or serves as a representative for, the other spouse in some context.
-
C.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
D.
spouseOfOfficeHolderJurisdiction
chosen
Indicates that one person is the spouse of a public office holder, with the relationship specifically tied to the jurisdiction in which that office is held.
-
E.
spouseOfHouse
Indicates a marital relationship between a person and a householder or head of household.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:11 p.m.