Triple
T8120341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Price |
E189589
|
entity |
| Predicate | spouseOfNotableAlias |
P32626
|
FINISHED |
| Object | Father of the Blues |
—
|
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: Father of the Blues | Statement: [Elizabeth Price, spouseOfNotableAlias, Father of the Blues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfNotableAlias Context triple: [Elizabeth Price, spouseOfNotableAlias, Father of the Blues]
-
A.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseAlsoKnownAs
chosen
Indicates that a person’s spouse is referred to by an alternative name or alias.
-
C.
hasNamesakeSpouse
Indicates that one entity has a spouse who shares the same name as another specified entity.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
marriedToNotablePerson
Indicates that a person is legally married to another individual who is widely recognized or notable.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.