Triple
T7519227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya April Moore |
E177724
|
entity |
| Predicate | WNBAAllStar |
P62658
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Maya April Moore, WNBAAllStar, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WNBAAllStar Context triple: [Maya April Moore, WNBAAllStar, 2011]
-
A.
isWNBAAllStar
chosen
Indicates that an individual has been selected as an All-Star player in the Women's National Basketball Association (WNBA).
-
B.
WNBAAllStarGameMVPInYear
Indicates that an entity was selected as the Most Valuable Player of the WNBA All-Star Game in a specified year.
-
C.
WNBAAllWNBAFirstTeamSelection
Indicates that an individual has been chosen for the WNBA All-WNBA First Team in a given season, recognizing them as one of the league’s top players at their position.
-
D.
WNBAAllDefensiveTeamSelection
Indicates that a player has been chosen for one of the WNBA All-Defensive Teams in a given season, recognizing their defensive performance.
-
E.
numberOfWNBAAllStarSelections
Indicates the count of times an individual has been selected to participate in the WNBA All-Star Game.
- 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_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. |
Created at: March 27, 2026, 3:46 p.m.