Triple
T5360112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William M. Jennings Trophy |
E102997
|
entity |
| Predicate | individualRecipientRole |
P37410
|
FINISHED |
| Object | goaltender |
—
|
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: goaltender | Statement: [William M. Jennings Trophy, individualRecipientRole, goaltender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: individualRecipientRole Context triple: [William M. Jennings Trophy, individualRecipientRole, goaltender]
-
A.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
B.
beneficiaryRole
chosen
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
-
C.
organizationRecipient
Indicates that an organization is the recipient or beneficiary of something provided, sent, or directed by another entity.
-
D.
positionOfRecipient
Indicates the spatial or contextual location associated with the recipient in a given interaction or transfer.
-
E.
typicalRecipientPosition
Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86330e4c8190b5452226886287b3 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.