Triple
T5265103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Vegas Aces |
E118918
|
entity |
| Predicate | draftedAjaWilsonOverallPick |
P36491
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Las Vegas Aces, draftedAjaWilsonOverallPick, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftedAjaWilsonOverallPick Context triple: [Las Vegas Aces, draftedAjaWilsonOverallPick, 1]
-
A.
WNBADraftPick
chosen
Indicates that one entity was selected as a draft pick by a WNBA team in the league’s draft.
-
B.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
C.
draftedFor
Indicates that one entity has been selected or assigned, typically through a draft process, to serve, play, or work for another entity.
-
D.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
E.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.