Triple
T23688067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Illustrated Sportsman of the Year |
E585220
|
entity |
| Predicate | hasTrophyOrCover |
P153392
|
FINISHED |
| Object | Sports Illustrated cover feature |
—
|
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: Sports Illustrated cover feature | Statement: [Sports Illustrated Sportsman of the Year, hasTrophyOrCover, Sports Illustrated cover feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrophyOrCover Context triple: [Sports Illustrated Sportsman of the Year, hasTrophyOrCover, Sports Illustrated cover feature]
-
A.
hasTrophyForm
Indicates that one entity exists in, or is characterized by, a special trophy-like form or version of another entity.
-
B.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
C.
hasRelatedTrophy
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
-
D.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
E.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5bfe15c8190af2b4c451bccae16 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.