Triple
T24568338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patsy Sutton |
E607857
|
entity |
| Predicate | hasSpouseHonor |
P71310
|
FINISHED |
| Object | Naismith Memorial Basketball Hall of Fame inductee |
—
|
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: Naismith Memorial Basketball Hall of Fame inductee | Statement: [Patsy Sutton, hasSpouseHonor, Naismith Memorial Basketball Hall of Fame inductee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseHonor Context triple: [Patsy Sutton, hasSpouseHonor, Naismith Memorial Basketball Hall of Fame inductee]
-
A.
spouseOfHonouree
Indicates that one person is the spouse (married partner) of the honouree.
-
B.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
C.
spouseNobilityStatus
Indicates that the predicate specifies the nobility rank or noble status held by a person’s spouse.
-
D.
spouseAwardedFor
Indicates that an award or honor was given to a person specifically because of, or in recognition of, their spouse’s achievements or status.
-
E.
spouseNotableAward
chosen
Indicates that a person’s spouse has received a notable award or honor.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9225d9c8190ae92e5540f6c45c2 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.