Triple
T7519239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya April Moore |
E177724
|
entity |
| Predicate | USBWANationalPlayerOfTheYear |
P77439
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Maya April Moore, USBWANationalPlayerOfTheYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USBWANationalPlayerOfTheYear Context triple: [Maya April Moore, USBWANationalPlayerOfTheYear, 2009]
-
A.
teammateOfTheYear
Indicates that one entity has been recognized or awarded as the outstanding or most valuable teammate in relation to another entity or within a shared team context.
-
B.
conferencePlayerOfTheYearFor
Indicates that an entity has been recognized as the player of the year within a specific athletic conference.
-
C.
NFLOffensivePlayerOfTheYear
Indicates that an entity was selected as the NFL Offensive Player of the Year for a given season or time period.
-
D.
AllStarGameMostValuablePlayer
Indicates that an entity was selected as the Most Valuable Player in an All-Star Game event.
-
E.
APNFLOffensivePlayerOfTheYear
Indicates that an entity was selected as the Associated Press NFL Offensive Player of the Year for a given season.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f98ae48190946a18d7c2d33bcd |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:46 p.m.