Triple
T22811260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverly D. Stakes |
E564680
|
entity |
| Predicate | namedForRelation |
P136469
|
FINISHED |
| Object | Wife of Richard L. Duchossois |
—
|
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: Wife of Richard L. Duchossois | Statement: [Beverly D. Stakes, namedForRelation, Wife of Richard L. Duchossois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForRelation Context triple: [Beverly D. Stakes, namedForRelation, Wife of Richard L. Duchossois]
-
A.
namedForRelationship
chosen
Indicates that one entity serves as the namesake or source of the name for another entity.
-
B.
namedForField
Indicates that one entity is named after, or in honor of, a particular field, discipline, or area of study.
-
C.
namedForFamily
Indicates that one entity is named in honor of, or derived from the name of, a particular family or family group.
-
D.
namedForFeature
Indicates that one entity is named after, or derives its name from, a particular feature or characteristic of another entity.
-
E.
pairedWithRelationshipName
Indicates that one entity is associated with another as a named pair within a specific relationship context.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d60186881908f6cb609c536dc91 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.