Triple
T33671232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton Oilers prospects |
E862623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports talent pipeline |
C30345
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: sports talent pipeline Context triple: [Edmonton Oilers prospects, instanceOf, sports talent pipeline]
-
A.
sports recruiting network
A sports recruiting network is a platform that connects athletes, coaches, and scouts to share performance data, highlight reels, and communication tools that facilitate talent discovery and recruitment decisions.
-
B.
talent scout
A talent scout is a professional who identifies, evaluates, and recruits individuals with exceptional skills or potential for organizations such as sports teams, entertainment agencies, or companies.
-
C.
sports school
A sports school is an educational institution that combines general academic instruction with specialized athletic training to develop students’ physical skills and competitive performance.
-
D.
sports scholarship program
A sports scholarship program is a structured initiative that provides financial aid and support to student-athletes based on their athletic talent, academic performance, and potential for contribution to school or organizational sports teams.
-
E.
Player development system
chosen
A player development system is an organized framework of processes, tools, and feedback mechanisms designed to systematically improve players’ skills, physical conditioning, tactical understanding, and psychological readiness over time.
- F. None of above.
Provenance (1 batch)
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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.