Triple
T22213360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA G League Elite Camp |
E549010
|
entity |
| Predicate | benefitForPlayers |
P487
|
FINISHED |
| Object | opportunity to improve draft stock |
—
|
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: opportunity to improve draft stock | Statement: [NBA G League Elite Camp, benefitForPlayers, opportunity to improve draft stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitForPlayers Context triple: [NBA G League Elite Camp, benefitForPlayers, opportunity to improve draft stock]
-
A.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
B.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
C.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
D.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
E.
primaryUseByPlayers
Indicates the main way in which players typically use or interact with the referenced entity.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2d607c81909511761b5563ddee |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.