Triple
T22865986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susan Holmes McKagan |
E567053
|
entity |
| Predicate | spouseInstrument |
P150027
|
FINISHED |
| Object | bass guitar |
—
|
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: bass guitar | Statement: [Susan Holmes McKagan, spouseInstrument, bass guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseInstrument Context triple: [Susan Holmes McKagan, spouseInstrument, bass guitar]
-
A.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
B.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
E.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f00f21081909b771610549c5757 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:38 p.m.