Triple
T3996509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC Player of the Year |
E87109
|
entity |
| Predicate | hasSeparateWomen'sAward |
P51490
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SEC Player of the Year, hasSeparateWomen'sAward, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparateWomen'sAward Context triple: [SEC Player of the Year, hasSeparateWomen'sAward, yes]
-
A.
hasSeparateAwardFor
chosen
Indicates that there exists a distinct, dedicated award specifically recognizing the related entity, separate from other general or combined awards.
-
B.
awardCategoryGender
Indicates that an award category is designated for recipients of a specific gender.
-
C.
winnerGender
Indicates the gender of the entity that is the winner in a given event or competition.
-
D.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
E.
hasNotableFirstFemaleWinnerYear
Indicates the year in which the first notable female winner associated with an entity achieved her win.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.